Thomas,

Thank you for your reply. The document has been updated accordingly, and then 
published:
https://www.rfc-editor.org/info/rfc9783

RFC Editor/ar

> On Jun 13, 2025, at 12:52 AM, Thomas Fossati <thomas.foss...@linaro.org> 
> wrote:
> 
> Hi Alice,
> 
> On Thu, 12 Jun 2025 at 23:37, Alice Russo <aru...@staff.rfc-editor.org> wrote:
>> 
>> Authors,
>> 
>> A final question as we prepare your document for publication -- this line 
>> exceeds the 69-character limit of the sourcecode element by 3 characters:
>>     / eat_profile /              265: "tag:psacertified.org,2023:psa#tfm",
>> 
>> For updating it, which of these options do you prefer? (or let us know if 
>> you prefer a different solution.) The line appears in Appendices A.1 and A.2.
>> 
>> - Option A: moved "265:" to the left 3 characters.
>> See https://www.rfc-editor.org/authors/rfc9783-optA-diff.html
> 
> This one.
> 
>> - Option B: wrapped the line (similar to how other lines are already wrapped 
>> within the same element).
>> See https://www.rfc-editor.org/authors/rfc9783-optB-diff.html
> 
> Not this one.  The problem with this approach is that the CBOR tooling
> interprets the new line in a text string literally (i.e.,
> "tag:psacertified.org,2023:ps\na#tfm" instead of
> "tag:psacertified.org,2023:psa#tfm").  This is not a problem with the
> byte strings.
> 
>> At this point, a reply from one author is sufficient.
>> 
>> Thank you.
>> RFC Editor/ar
>> --
>> 
>> The current files:
>>> https://www.rfc-editor.org/authors/rfc9783.txt
>>> https://www.rfc-editor.org/authors/rfc9783.pdf
>>> https://www.rfc-editor.org/authors/rfc9783.html
>>> https://www.rfc-editor.org/authors/rfc9783.xml
> 
> cheers, thanks!
> t

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to