| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello, Gabor, Gabor.Bajko@nokia.com wrote: Qiaobing, The above sounds to me like a convenience but not a requirement. Of course it doesn't have to be globally unique in all cases, but uniqueness may be required in some scenarios. Precisely! Among the following specifications:What makes even less sense is to require the MN to construct an identifier with local scope when it has a bunch of globally unique identifiers available. We tend to overspecify things and the MIHFID doesn't seem to be an exeption ... 1) "One shall choose an MIHF_ID that is unique in the scope where the MIHF operates" (Qiaobing wants) 2) "One shall choose an MIHF_ID that is globally unique" (Michael wants) 3) "One shall choose an MIHF_ID that already exists AND is globally unique" (Gabor wants) I would say Gabor's version is the most overspecified :-) And it is 'Star Alliance', without the 'z' in it :) Be careful. That one is trademarked :-) regards, -Qiaobing |