Re: LFBLinkType's FromPortGroup definition?
"Joel M. Halpern" <[email protected]>
| Newsgroups | gmane.ietf.forces |
|---|---|
| Message-ID | <[email protected]> |
If the WG can agree on a suitable maximum length, I am happy to specify it. I could not come up with one. I highlighted the issue to the WG, and no one wanted to specify a maximum. So I left it unspecified. Yours, Joel M. Halpern At 09:46 PM 9/26/2006, Jia Fenggen wrote: >I partially agree with you but even though >filling or trimming maybe needed I still think >we should place a max length on the name to >allow the validation of the name on CE .I reserve the idea. >Yours,Fenggen >>From: "Joel M. Halpern" <[email protected]> >>Reply-To: "Joel M. Halpern" <[email protected]> >>To: [email protected] >>Subject: Re: LFBLinkType's FromPortGroup definition? >>Date: Tue, 26 Sep 2006 09:43:07 -0400 >> >>Given that the full topology is fetched only >>once in a great while, I am not concerned with >>picking a representation that is easy to >>encode. A few bytes on the wire per link is not a big deal. >> >>Also, I do not want to mandate that the names >>be fixed length, since then we have to mandate >>fill, and recommend trimming for presentation >>to the user, etc. All things I would rather stay away from. >> >>Yours, >>Joel M. Halpern >> >>At 06:57 AM 9/26/2006, Jia Fenggen wrote: >>>In FE object LFB definition,when we describe >>>LFB topology with LFBLinkTypes in which we >>>define FromPortGroup as string the size of >>>which is variable,should we use a fixed size >>>string because when it is we have to use >>>another FULLDATA TLV to encode each >>>LFBLinkType? There are other places string >>>type is used,I will not list them all. >>> <name>LFBLinkType</name> <synopsis> >>> Link between two LFB instances of topology >>></synopsis> <struct> >>><element elementID="1"> <name>FromLFBID</name> >>><synopsis>LFB src</synopsis> >>><typeRef>LFBSelectorType</typeRef> </element> >>><element elementID="2"> >>><name>FromPortGroup</name> <synopsis>src port >>>group</synopsis> <typeRef>string</typeRef> >>></element> >>> >>>_________________________________________________________________ >>>Ãâ·ÑÏÂÔØ MSN Explorer: http://explorer.msn.com/lccn/ > >_________________________________________________________________ >ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn