| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
I had this action item from the call:
* Phil - Propose new TLV
flags to support notion of context ID - to convey sectors, frequency assignment
and subnet/prefix/access router ID - by 6/8/04
A 'Sector ID' in the form of a BS MAC ID prefix,
suffix, or additional message advertisement through DCD (and, by implication
through NBR-ADV) has already been proposed by Samsung and I am just going to
refine this idea. Allowing for the bifurcation the existing BS MAC ID,
exactly as proposed by Samsung, seems the best approach since it encourages
fewer changes in other places in the document affecting, among other things,
NBR-ADV messages.
I was planning on borrowing ARID use proposed in
802.21 and advertising it through NBR-ADV. Sticking ARID into DCD seems
overkill. And we don't need ARID in RNG-RSP or SBC-RSP because I am
already going to propose some HO/network re-entry flags in RNG-RSP that will
cover that.
My question concerns the FA (frequency assignment)
element. My question is, wouldn't the sector DCD have the required
information for FA? Do we actually require additional MAC level
information for advertising FA? I think by definition, each sector would
have its own DCD, though for sectored BS using a single frequency/channel
assignment, that DCD would be identical. For sectored BS using different
frequencies/channel assignments in each sector, the DCD would necessarily
be different. And since DCD is imbedded in NBR-ADV, we get appropriate
neighbor advertisement as well.
I would appreciate feedback on this item prior to
my scheduled due date for submission.
Thanks,
Phil |