This is how it is expected to work for no-mod items... The algorithm is a bit confusing, however, and I think you still can find the explanation for it on Marine's blog (it's a very old post, dating from the first RLV year back in 2007 or so).
Here is how it works: when an object is attached from inside the #RLV folder, RestrainedLove attempts to rename the object so that the name contains "(attachment_point)" (this is to keep track of where each object is supposed to be attached by the server on "attach on default joint" request and find out by looking at its name before sending that request or not to the server, depending on what other objects are worn on the same attachment point and their locked status).
Of course, this cannot work for no-mod items (since you can't rename them). In the latter case, RestrainedLove checks whether the item is at least two levels under the #RLV folder (i.e. whether it's an outfit sub-folder) and if so, renames that folder into ".(attachment_point)" (the "." got a special meaning for RestrainedLove: it denotes an "invisible" folder that will not be taken into account by folder-browsing RLV commands).
So, when using no-mod objects (that don't already have their name with "(attachment_point)" in them, which could happen...) in #RLV outfits, you should place them inside a sub-folder of that outfit (simply create a "New Folder" and place the no-mod object in it: that sub-folder will be renamed on first attachment).
In your case, you should use:
Which, once "outfitname" worn the first time, will turn into: