[rfc-i] Re: Minimal GitHub AUTH48

2025-09-18 Thread Michael Richardson
ld be good if the RPC could say to authors > ahead of time how the authors should interact with the PR (just as they > are told how to respond to AUTH48 email). THe suggestion mechanism has some limits: it can't edit any text that wasn't already touched.I'm curious ho

[rfc-i] Re: Intake form: an experimental RPC process for docs entering the RFC Editor Queue

2025-07-09 Thread Michael Richardson
Jean Mahoney wrote: > Hi all, > On 7/8/25 10:31 PM, Michael Richardson wrote: >> Jay Daley wrote: > The AUTH state is not a >> new state but an existing one - see > >> https://authors.ietf.org/en/rfc-publication-process for the full state

[rfc-i] Re: Intake form: an experimental RPC process for docs entering the RFC Editor Queue

2025-07-08 Thread Michael Richardson
we use it". These are not terrible things, but again, I'd rather it happen earlier if possible. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___

[rfc-i] Re: [Rswg] Re: Re: [rsab] Call for comments: (RFC Editor Model (Version 3))

2025-06-17 Thread Michael Richardson
tally boils down to not drinking enough beer with others. We want to be a value-based culture, and that means establishing principles, not proceedures [%]- no, not my dad. He died in 2003. My dad's best friend.) -- Michael Richardson. o O ( IPv6 IøT co

[rfc-i] Re: RFC 9633 SVG is unreadable

2025-05-16 Thread Michael Richardson
t a diagram itself. Both so that I can zoom better, but also so that I can extract the diagram for a slide, etc. I usually wind up diving into the XML or HTML and yanking the part out into a file. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson

[rfc-i] Re: swagger APIs

2025-05-15 Thread Michael Richardson
Eliot Lear wrote: > Not an RFC yet, but see draft-ietf-scim-device-model.  While it's not super > obvious, the reference should probably be > https://spec.openapis.org/oas/v3.1.1.html. and you used YAML rather than JSON representation. -- Michael Richardson , Sand

[rfc-i] Re: Normative information in RFC imagery

2025-05-15 Thread Michael Richardson
HTML table is generally accessible for screen readers, which know how to > tab between cells. Is the CSV for people who use the TXT file? Or maybe I'm > misunderstanding? It would all be tables, but the source form might be CSV. -- Michael Richardson , Sandelman Software Work

[rfc-i] Re: swagger APIs

2025-05-15 Thread Michael Richardson
t, I don't see anything in the References that refers to the specification. This is really the core of my question. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS* signature.asc Description: PGP signature

[rfc-i] Re: swagger APIs

2025-05-15 Thread Michael Richardson
r that exposes the files as resources. I like this as an idea. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS* signature.asc Description: PGP signature ___ rfc-interest mailing list

[rfc-i] swagger APIs

2025-05-14 Thread Michael Richardson
WG's NIPC document. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS* signature.asc Description: PGP signature ___ rfc-interest mailing list -- rfc-interest@rfc-editor.org To unsubs

[rfc-i] Re: Normative information in RFC imagery

2025-05-14 Thread Michael Richardson
> A fourth path has been suggested: using a formal language to describe > diagrams. UML was suggested as a possibility. I have not yet found > convincing evidence that UML alone is sufficiently accessible to people > with visual disabilities. UML is useless to me. Too com

[rfc-i] Re: Normative information in RFC imagery

2025-05-14 Thread Michael Richardson
er. I think that this is the right message: let us help you. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS* signature.asc Description: PGP signature ___ rfc-interest mailing list -- r

[rfc-i] Re: Normative information in RFC imagery

2025-05-14 Thread Michael Richardson
high production values. kramdown has many ways to "shell out" to get nice swim diagrams, and other things. We probably need a few more popular choices (I mean: best practices that are well documented), and to socialize those choices. -- Michael Richardson , Sandelman Software Works -

[rfc-i] Re: Manuscript style (Re: Report from the first-ever high-level RPC Retreat)

2025-04-24 Thread Michael Richardson
Jean Mahoney wrote: > On 4/24/25 1:52 PM, Michael Richardson wrote: >> Paul Hoffman wrote: >> > This thread has become very author-hostile. "You are forced to deal >> > with changes that are being made to match some people's preferred

[rfc-i] Re: Manuscript style (Re: Report from the first-ever high-level RPC Retreat)

2025-04-24 Thread Michael Richardson
Paul Hoffman wrote: > This thread has become very author-hostile. "You are forced to deal > with changes that are being made to match some people's preferred > viewing of your source material." That's exactly what the RPC does today. If the author hasn't used NSNL, then ANY diff the

[rfc-i] Re: Manuscript style (Re: Report from the first-ever high-level RPC Retreat)

2025-04-24 Thread Michael Richardson
Ted Lemon wrote: > On Thu, Apr 24, 2025, at 6:13 AM, Michael Richardson wrote: >> The question remains, when the RPC edits text, whether XML or kramdown, >> ought they do a do-nothing pass where they change to NSNL. >> Assume that there is a tool to do this.

[rfc-i] Re: Manuscript style (Re: Report from the first-ever high-level RPC Retreat)

2025-04-24 Thread Michael Richardson
to. (Because comments on ML are usually about section 4.3.2) All of the above then goes against people who then open the document XMLmind, and then save it, and then wonder why every single line is a diff. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman S

[rfc-i] Re: Report from the first-ever high-level RPC Retreat

2025-04-23 Thread Michael Richardson
hat the people we want to reach don't come to the plenary. Were it me, I'd do a commit where I *just* wrapped things. > Obviously, these lines are going to be a bit blurry, but I think if > we can agree on the general concept, we'll be in a much better > place. Ag

[rfc-i] Re: Manuscript style (Re: Report from the first-ever high-level RPC Retreat)

2025-04-23 Thread Michael Richardson
t, but 80% of readers' MUA will wrap it and the point will be lost) -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works|IoT architect [ ] m...@sandelman.ca http://www.sandelman.ca/

[rfc-i] Re: Report from the first-ever high-level RPC Retreat

2025-04-23 Thread Michael Richardson
ext week. I doubt it will compile for WSL, it just barely compiles on Linux. (The author runs a fork of NetBSD that he maintains) Carsten suggests that magit.el might also do this, and I installed it, but I haven't used it yet. -- Michael Richardson. o O ( IPv6 IøT consulting )

[rfc-i] Re: Report from the first-ever high-level RPC Retreat

2025-04-22 Thread Michael Richardson
) might be useful in order to turn on copy-editing pass into multiple commits for review. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___

[rfc-i] Re: Report from the first-ever high-level RPC Retreat

2025-04-18 Thread Michael Richardson
ing it out there and reliable has been difficult} -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ rfc-interest mailing list -- rfc-intere

[rfc-i] Re: Report from the first-ever high-level RPC Retreat

2025-04-17 Thread Michael Richardson
er mind. Not possible like that. github can render markdown, and can show diffs to markdown in red/green text, and during the I-D process, that's really useful. It's a reason why many would like the editorial pass from the RPC to occur in markdown rather than XML. -- Michael R

[rfc-i] Re: Can we add ORCIDs to the XML vocabulary?

2025-04-12 Thread Michael Richardson
ust like email or uri, but the idea is that > it contains your ORCID, like this: It all works for me. I'm just not clear we are at a point in the xml process where we can actually do amendments. It seems that we have been spinning wheels on this for along time. -- Michael Richa

[rfc-i] Re: [saag] RFCs vs Standards

2024-12-11 Thread Michael Richardson
said the RPC was doing this. I think it is worth reposting this more widely. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ rfc-intere

[rfc-i] Re: [saag] Re: RFCs vs Standards

2024-12-11 Thread Michael Richardson
t; problems that I-Ds have. It would great if we could have an IETF gitlab, so that we could argue less about github vs git. Document repos on *github* become attractive nuissances, making people not familiar with the IETF process think they can write PRs long after the document has become

[rfc-i] Re: [saag] Re: RFCs vs Standards

2024-12-11 Thread Michael Richardson
er http://geocities.com/rsalz/my-pet-protocol.txt -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ rfc-interest mailing list -- rfc-intere

[rfc-i] Re: [saag] Re: RFCs vs Standards

2024-12-05 Thread Michael Richardson
e", and for which the principles of open-stand.org applied. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works|IoT architect [ ] m...@sandelman.ca http://www.sandelman.ca/| ruby on

[rfc-i] Re: RFCs vs Standards

2024-12-03 Thread Michael Richardson
S Moonesamy wrote: > I removed the IETF mailing list (SAAG) from the Cc. Good, so did my reply-to. > At 09:12 AM 01-12-2024, Michael Richardson wrote: >> Over in saag@, there is a multi-week long debate about whether/how to publish >> algorithm allocations

[rfc-i] Re: [saag] Re: RFCs vs Standards

2024-12-01 Thread Michael Richardson
Stephen Farrell wrote: > On 01/12/2024 17:12, Michael Richardson wrote: >> I think that the very-big-tent collective "we" have benefitted >> greatly from the multi-decade ambiguity about the RFC series. > If the above is the case, why do you think w

[rfc-i] RFCs vs Standards

2024-12-01 Thread Michael Richardson
Over in saag@, there is a multi-week long debate about whether/how to publish algorithm allocations which are not the result of IETF consensus. Some feel that Specification Required is not strong enough, others feel it is too strong, with the quasi-temporary nature of I-Ds intruding into the deba