Dear all,

Thank you very much to the authors and the RFC Production Center for the
hard work on this. I agree with the changes, including the latest
corrections such as those in Figures 18 and 19. The draft updates are
mostly editorial and improve clarity, consistency, and RFC style without
changing the technical substance. Overall, the edits look good and helpful,
and they make the document easier to read and less ambiguous.

Best Regards,

Ines.

On Sat, Mar 21, 2026 at 11:26 AM Pascal Thubert <[email protected]>
wrote:

> Hello Michael
>
> The skew seems to be coming from tabs in my editor.
> I reviewed your changes and have no issue with them.
>
> I believe that we need to add a P before or above the DAO the figure 18
> like below:
>
> 18 would become
>
>         ------+---------
>               |          Internet
>               |
>            +-----+
>            |     | Border Router
>            |     |  (RPL Root)
>            +-----+                      | P-  ^                   |
>               |                         | DAO | P-DAO-ACK         |
>         o    o   o    o                 |     |                   |
>     o o   o  o Ingress  o  o  o         |  ^       | Projected    .
>    o  o o  o    o  \\  o  o    o        |  | P-DAO | Route        .
>    o   o    o  o    \\  o    o  o  o    | ^        |              .
>   o  o   o  o   o    Egress   o o       v | P-DAO  v              .
>   o          o   LLN   o   o     o                                |
>       o o   o        o     o              Loose Source Route Path |
>    o       o      o    o                                          v
>
>
>
> figure 19 looked OK to me but maybe like below it is clearer?
>
>            ------+---------
>                  |          Internet
>                  |
>               +-----+
>               |     | Border Router
>               |     |  (RPL Root)
>               +-----+                    | P-  ^ P-DAO-ACK
>                  |        Track          | DAO |
>            o    o   o    Ingress         V     |
>        o o   o  o   o  o     X   o                X Source-
>       o  o o  o o    o   o     X    o  o          X Routed
>       o   o    o  o     o   o    X     o          X Segment
>      o  o   o  o   o  o    o  o    X              X
>                                  Egress
>         o  o  o  o           o     |
>                                  Target
>        o       o     LLN          o
>      o          o             o     o
>
>
> all the best;
>
> Pascal
> Le sam. 21 mars 2026 à 02:50, Michael Richardson <[email protected]>
> a écrit :
>
>>
>> Michael Richardson <[email protected]> wrote:
>>     > I found though:
>>
>>     > Figure 3 seems askew, the ^v route between S and D is hard to read.
>>     > Figure 4 is better, but might also be better aligned.
>>     > Figure 7 has skew and some other issues... like this line of ._-
>> under
>>     > "Southbound API"
>>     > I checked .html and .txt to be sure it wasn't just the red/green
>> markup.
>>     > Figure 18... not sure if there is a problem.
>>     > Figure 19, definitely a problem.
>>
>> Hi, I edited the XML slightly, and put it here:
>> https://www.sandelman.ca/tmp/rfc9914-authors-fixed-figures.xml
>>
>> I think it fixes 3,4,19.
>> I fixed some things on figure 7.
>> I don't know if I got 18.
>>
>> --
>> Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting
>> )
>>            Sandelman Software Works Inc, Ottawa and Worldwide
>>
>>
>>
>>
>>
>
> --
> Pascal
>
-- 
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to