Certainly. The VENDOR-CONSTRAINT TLV could be formatted this way (similar to the VENDOR-CONSTRAINT object)
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Enterprise-Specific Information ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ If only the VENDOR-CONSTRAINT object is possible, it is necessary somewhere in the VENDOR-CONSTRAINT object to give additional information, so that it is possible to correlate the contents of the VENDOR-CONSTRAINT object with other objects in the message. By having a VENDOR-CONSTRAINT TLV, that TLV can be directly added to the object for which such additional information is wanted. Examples of use of VENDOR-CONSTRAINT TLV are as follows. * in PCNtf messages for vendor specific additions; * in END-POINTS object, specifically the Generalized Endpoints object type, with vendor specific additions The addition of a VENDOR-CONSTRAINT TLV would free me from picking an unused value for the Type. The type I have picked is currently unused, but may be assigned in the near future, and then follows the general problem of updating not just future software (which is simple), but also existing software already delivered to customers (which is not so simple). Christian ________________________________________ From: Fatai Zhang [zhangfa...@huawei.com] Sent: Wednesday, May 11, 2011 05:14 To: Kaas-Petersen Christian; pce@ietf.org Subject: Re: [Pce] VENDOR-CONSTRAINT Hi Christian, Thanks for your comments. Could you explain a little more about what are requirements for the VENOR-CONSTRAINT TLV? Why VENOR-CONSTRAINT object can not meet these requirements? How many (and which) objects should be extended to include VENOR-CONSTRAINT TLV? Thanks Fatai Huawei Technologies Co., LTD. Huawei Base, Bantian, Longgang, Shenzhen 518129 P.R.China Tel: +86-755-28972912 Fax: +86-755-28972935 ----- Original Message ----- From: christian.kaas-peter...@tieto.com<mailto:christian.kaas-peter...@tieto.com> To: pce@ietf.org<mailto:pce@ietf.org> Sent: Monday, May 09, 2011 2:26 PM Subject: [Pce] VENDOR-CONSTRAINT draft-ietf-pce-vendor-constraints-04 describes a new VENDOR-CONSTRAINT object. I should like the draft also to introduce a VENDOR-CONSTRAINT TLV allowing vendor specific additions to for example the END-POINTS object. Christian ________________________________ _______________________________________________ Pce mailing list Pce@ietf.org<mailto:Pce@ietf.org> https://www.ietf.org/mailman/listinfo/pce _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce