|
> Ultimately, it's the NAS that has to provision services based on the content > of the Extended Attributes, so the fact that the NAS understands them is of > prime importance. I agree. > The fact the proxies understand them is only of > importance if the proxies are expected to be "editing" the attributes passed > to and from the NAS. If a particular proxy is know to indiscriminately > discard VSAs, then knowing it supports Extended Attributes may be of greater > importance that otherwise might be the case. RFC 2865 Section 5.26 states that robust implementation should treat the values of VSAs as opaque text. So a proxy complying with that recommendation should be able to pass Extended Attributes in either direction without corrupting them. Such an existing proxy should also be able to remove or add VSAs by treating them as opaque blobs. However, this wouldn't necessarily allow proxies to remove or add individual Extended Attributes, just to selectively add or remove VSAs within which Extended Attributes are encapsulated. For a proxy to be able to add, remove or modify specific Extended Attributes would require parsing the Extended Attribute format. |