Creating an LDN inbox in a uniform way

Hi all!
I was wondering whether adding the creation of inbox resources to the protocol is under consideration? The current specification limits itself to LDN compliance and the LDN recommendation does not cover this aspect.

This issue can be generalized to adding the http://www.w3.org/ns/ldp#inbox (or others, if you want to expand the scope) link when creating a container. I guess you can always add <> ldp:inbox <http://localhost/resource-inbox/> to your PUT request, but I was wondering what other uniform options there are?

E.g, the community server supports the following (see also https://github.com/solid/community-server/issues/1027):

In the Solid Community Server, an inbox can be registered for a specific resource by specifying a Link header with value <http://localhost/resource-inbox>; rel="http://www.w3.org/ns/ldp#inbox" when creating a resource.

Example request:

1 PUT /resource HTTP/1.1
2 Host: localhost
3 Content-Type: text/turtle
4 Link: <http://localhost/resource-inbox/>; rel="http://www.w3.org/ns/ldp#inbox"

It makes perfect sense that this is out of scope for LDN, but for Solid, the applications might require inboxes and therefore need a standardized way to create inboxes. Or is this something the data pod should do, and if so, how do you create guarentees that there will ever be an inbox?

Start by reading the linked LDN recommendation and the referenced Solid Community Server issue about inbox registration. Clarify whether the specification should define a uniform inbox-creation mechanism and whether the data pod must guarantee an inbox; done requires an agreed scope and documented protocol behavior.