Hi Maciek and Vratko,

Thank you for the clarification and links! I've retrieved the markdown files, 
so now we can process as usual.

Sincerely,
Sarah Tarrant
RFC Production Center

> On Nov 14, 2025, at 5:17 PM, Maciek Konstantynowicz (mkonstan) 
> <[email protected]> wrote:
> 
> Hi Sarah,
> 
> Please see inline.
> 
> Cheers,
> -Maciek and Vratko (authors)
> 
> 
> > From: Sarah Tarrant <[email protected]>
> > Date: Friday, 14 November 2025 at 21:35
> > To: Maciek Konstantynowicz (mkonstan) <[email protected]>
> > Cc: Vratko Polák -X (vrpolak - PANTHEON TECH SRO at Cisco)
> > <[email protected]>, [email protected]
> > <[email protected]>, [email protected]
> > <[email protected]>, [email protected]
> > <[email protected]>, [email protected]
> > <[email protected]>
> > Subject: Re: Document intake questions about
> > <draft-ietf-bmwg-mlrsearch-15>
> > 
> > Hi Maciek,
> > 
> > Thank you for your reply!
> > 
> > A) Regarding:
> > >> 6) This document uses one or more of the following text styles.
> > >> Are these elements used consistently?
> > >>
> > >> ...
> > >>
> > >>  * italics (<em/> or *)
> > >
> > > Currently yes, but we prefer converting them to bold instead.
> > 
> > 
> > Would you like us to update italics (<em/>) to bold (<strong/>)?
> 
> Yes, please.
> 
> > 
> > 
> > B) Regarding your request to participate in the markdown experiment, I
> > wasn't able to find the markdown file on GitHub. Could you please send
> > along a self-contained file?
> 
> Here is the .md source of -15:
> 
> https://git.fd.io/csit/tree/docs/ietf/draft-ietf-bmwg-mlrsearch-15.md
> 
> And mirror in github.com:
> 
> https://github.com/FDio/csit/blob/master/docs/ietf/draft-ietf-bmwg-mlrsearch-15.md
> 
> > 
> > Thank you,
> > Sarah Tarrant
> > RFC Production Center
> > 
> > > On Nov 14, 2025, at 12:50 PM, Maciek Konstantynowicz (mkonstan) 
> > > <[email protected]> wrote:
> > >
> > > Currently yes, but we prefer converting them to bold instead.


-- 
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to