My thoughts, I’d also include the ‘protocol’ eg (RADIUS, DHCP, Diameter (Sometime in a future world)) so it could be: <keyword> [virtual-server].[protocol].<packet-type> { <sub-request-attr0> := <parent attr0> <sub-request-attr1> += <parent attr1> <sub-request-attrN> += <parent attrN> } Now for what that keyword should be “child” sounds okay but that’s not perfect by any means. Note: I think async should be a generic parallel concept to allow other types of use. For example log to db1, db2, db3 and answer if one returns ok. Or send json trigger without waiting for it to answer or… Alister On 07/09/2017, 07:28, "Freeradius-Users on behalf of Arran Cudbard-Bell" <freeradius-users-bounces+alister.winfield=sky.uk@lists.freeradius.org on behalf of a.cudbardb@freeradius.org> wrote: New functionality is being added in v4.0.x to allow new sub-requests to be generated by requests received by the server. The basic format is: <keyword> [virtual-server.]<packet-type> { <sub-request-attr0> := <parent attr0> <sub-request-attr1> += <parent attr1> <sub-request-attrN> += <parent attrN> } There's debate about what <keyword> should be, and whether there should be multiple <keywords> for async - where we split the lifetime of the sub-request from its parent, and synchronous behaviour - where we wait for the sub-request to return before we continue processing. The original keyword was "fork", and has since been changed to "create". Do people have any opinions on what the easiest to infer and most consistent keyword to use here would be? Some other ideas were "spawn", and "child". There's no guarantee that the most popular keyword/idea will be used, but it'll at least inform us of general public opinion :) -Arran Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of Sky plc and Sky International AG and are used under licence. Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of Sky plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.