Re: Typo in an IPv6 address in USEPRO

Julien ÉLIE <[email protected]> writes:

> 3.2.2.  Path Header Field Example
>
>       Path: foo.isp.example!.SEEN.isp.example!foo-news
>         !.MISMATCH.2001:DB:0:0:8:800:200C:417A!bar.isp.example
>         !!old.site.example!barbaz!!baz.isp.example
>         !.POSTED.dialup123.baz.isp.example!not-for-mail
>
>   This article was injected by baz.isp.example as indicated by the
>   <diag-keyword> "POSTED".  The injector has recorded that it received
>   the article from dialup123.baz.isp.example. "not-for-mail" is a
>   common <tail-entry>.
>
> ** Still a missing (double) space before "not-for-mail" (otherwise, in case
> ** it is a bug in the converter into text, a semicolon ";" could be used).

This is a tool limitation.  In the XML source, there is a newline after
that period and "not-for-mail" is on the next line.  xml2rfc doesn't use
two spaces after the period when reflowing the paragraph.

The paragraph currently uses one sentence per concept, and the part about
not-for-mail is not the same concept as the previous sentence.  I'm
hesitant to fiddle with the grammar to work around a minor rendering flaw
in the converter.

>   bar.isp.example relayed it to foo-news, which, not being convinced
>   that it truly came from bar.isp.example, inserted the <diag-keyword>
>   "MISMATCH" and then stated that it received the article from the IPv6
>   address [2001:DB8:0:0:8:800:200C:417A].
>
> ** The IPv6 address is not the same between the sample and its comment.
> ** I think (or better say Google hints that) the right one is the second one,
> ** with "DB8".

Thanks, I'll try to get this fixed.

-- 
Russ Allbery ([email protected])             <http://www.eyrie.org/~eagle/>