Hi Esko, I would also assume that the constraint part is the pledge in the first place, which may take over the role of a join proxy. If the intention is to emphasize that the pledge is constraint my favorite out of the 3 would be _Join Proxy for Lightweight Bootstrapping Protocols_. I would understand the other two more in the direction of "reduced functionality" either of the network or the bootstrapping protocol itself.
A further alternative may be _Join Proxy for Bootstrapping of Constrained Network Elements_ Best regards Steffen > -----Original Message----- > From: Anima <[email protected]> On Behalf Of Esko Dijk > Sent: Tuesday, September 5, 2023 2:08 PM > To: Michael Richardson <[email protected]>; [email protected] > Subject: Re: [Anima] title for join proxy document > > I typically assumed the Pledge/joiner would be a constrained device, and also > the > Join Proxy would be a constrained device: in a mesh situation typically a > Joiner > that just successfully joined starts to operate as Join Proxy for any future > Pledges. > And these devices would operate in a constrained network. > > Here some potential titles to reflect that: > > _ Join Proxy for Bootstrapping Protocols in Constrained Networks_ > > _ Join Proxy for Constrained-Network Bootstrapping Protocols _ > > _ Join Proxy for Lightweight Bootstrapping Protocols _ > > > These titles do not make a claim about whether the Join Proxy itself is a > constrained device, or not. That could be said in the intro, that it *could* > be a > constrained device. > > Esko > > -----Original Message----- > From: Anima <[email protected]> On Behalf Of Michael Richardson > Sent: Monday, September 4, 2023 19:22 > To: [email protected] > Subject: [Anima] title for join proxy document > > > Russ points out that the title is a slightly mis-leading. > https://github.co/ > m%2Fanima-wg%2Fconstrained-join- > proxy%2Fissues%2F51&data=05%7C01%7Csteffen.fries%40siemens.com%7C487 > 6268a6fc84d0d75b008dbae08bb1a%7C38ae3bcd95794fd4addab42e1495d55a% > 7C1%7C0%7C638295124751198185%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM > C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7 > C%7C%7C&sdata=VF3luW2aud0xbKTZVNGDTyaENEY0BM9%2BnYOicyegWUU% > 3D&reserved=0 > > The document is titled: > _Constrained Join Proxy for Bootstrapping Protocols_ > > --- abstract > This document extends the work of Bootstrapping Remote Secure Key > Infrastructures (BRSKI) by replacing the Circuit-proxy between > Pledge and Registrar by a stateless/stateful constrained Join > Proxy. The constrained Join Proxy is a mesh neighbor of the > Pledge and can relay a DTLS session originating from a Pledge with only > link-local > addresses to a Registrar which is not a mesh neighbor of the > Pledge. > > This document defines a protocol to securely assign a Pledge to a domain, > represented by a Registrar, using an intermediary node between Pledge and > Registrar. This intermediary node is known as a "constrained Join > Proxy". An enrolled Pledge can act as a constrained Join Proxy. > > {paragraph two is most definitely wrong, but paragraph one is absolutely > correct} > > Russ is wrong in thinking that the join proxy machine is not constrained; it > may > well be, and that's why we want to reduce/eliminate state if possible. > (Or rather, move it into the network and into the Registrar) > > However, I stubbed my toe on the title while trying to fix things. > > It is the (Constrained Join) Proxy for Bootstrapping Protocols. > Not, the: (Constrained Join Proxy) for Bootstrapping Protocols_ > > I thought about instead: > Stateless Join Proxy for Constrained Bootstrapping Protocols > > Or even s/Bootstrapping/Onboarding/ > but, actually we document both State and Stateless mechanisms. > > Please help me fix the title and from that, the abstract. > > -- > Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > > _______________________________________________ > Anima mailing list > [email protected] > https://www.ietf/. > org%2Fmailman%2Flistinfo%2Fanima&data=05%7C01%7Csteffen.fries%40sieme > ns.com%7C4876268a6fc84d0d75b008dbae08bb1a%7C38ae3bcd95794fd4addab > 42e1495d55a%7C1%7C0%7C638295124751198185%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0% > 3D%7C3000%7C%7C%7C&sdata=EJySSvA%2BRpV0PxJwke%2BynJD8rpklLYswDd > 6szPITpG8%3D&reserved=0 _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
