Hi Alan, On 4 Jan 2012, at 15:19 , Alan DeKok wrote: > That won't work. The type/ext-type is used to uniquely identify an > attribute. As the RFC6158 says, the interpretation of the attribute is > based solely on the type code(s). What you're doing above is changing > the meaning of the attribute based on its length. > > That's difficult, if not impossible, to do correctly.
I'm afraid there is a misunderstanding. The Chunked-Atrribute is an attribute on its own that contains only a reference to the attribute being chunked. It has to appear in all the packets containing chunks of attributes, as many as attributes they refer to. Chunks are intended to be encoded following the usual encoding methods. It is true that the layout and the field names used in it are misleading (instead of "Ext-Type" we should call it "Type-ID" or "Attribute-ID" or something similar), and you are right in that the way of specifying this identifier should be better aligned with the way of coding types and extended types. > Attributes can also occur multiple times in a packet, with different > values. e.g. Proxy-State. You are right. That should be addressed. A simple proposal could follow these rules: * Chunked-Attribute must appear before the attribute it refers to in the packet * If an attribute occurs multiple times in a request/response (we cannot speak here of "a packet") chunks for only one of the occurrences, associated to the corresponding Chunked-Attribute, are allowed in a given packet * Non-fragmented values for this attribute can appear in any packet, but always before the Chunked-Attribute that refers to it * As many Chunked-Attribute (and referred attributes) may appear in a given packet as necessary. > If this document is published soon after the extensions document, then > it has a better likelihood of being implemented. Good point! Be goode, -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D e-mail: [email protected] Tel: +34 913 129 041 Mobile: +34 682 051 091 ----------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
