RE: new seqnum text; was ieee1904_3_D02_20151113_clean-seqnum-jik.docx
Yasser,
Yes the value is static after initializing it and for the lifetime of the flow. I should have clarified that. No intention to "secretly" introduce the third counter.
- Jouni
> -----Original Message-----
> From: Yasser Kilde Bajwa [mailto:Yasser.Bajwa@xxxxxxxxxxxx]
> Sent: Monday, November 23, 2015 9:42 PM
> To: Jouni Korhonen; stds-1904-3-tf@xxxxxxxx
> Subject: RE: new seqnum text; was ieee1904_3_D02_20151113_clean-
> seqnum-jik.docx
>
> Hi Jouni,
>
> Sure, maybe I am being overly pedantic but I always think it is a bit risky to
> leave such fields too open for interpretation. If we state that this value can
> be set to a certain value and that will remain the same for the entire course
> of the transmission then I agree with you, it would be exactly the same as
> having 0's. However, if we leave it open for interpretation then someone
> might decide to implement a third counter in this part while other
> implementations are designed just for static values. Or maybe some time-
> critical value that will only be set aligned with a certain point in the frame. We
> have actually been caught out like this in earlier protocols which is why I was
> just trying to understand how we wanted to use this field.
>
> Best regards
>
> Yasser Kilde Bajwa
> IP Core Product Manager
> MTI Mobile
> An MTI Company
>
> Krakasvej 17, 3400 Hilleroed, Denmark
>
> T: +886 908161200
> E: Yasser.Bajwa@xxxxxxxxxxxx
> W: www.mti-mobile.com / www.mtigroup.com
>
> This message is confidential and intended only for the addressees named
> therein. The message may contain legally privileged information or be
> otherwise protected by law. If you are not the intended recipient, please let
> the sender know by return email and immediately delete this message and
> its attachments without reading, copying or printing it or disclosing its
> contents to anyone.
>
>
> === MICROELECTRONICS TECHNOLOGY INC. ===
> This message (and any attachments) may contain information that is
> confidential, proprietary, privileged or otherwise protected by law. The
> message is intended solely for the named addressee (or a person
> responsible for delivering it to the addressee). If you are not the intended
> recipient of this message, you are not authorized to read, print, retain, copy
> or disseminate this message or any part of it. If you have received this
> message in error, please destroy the message or delete it from your system
> immediately and notify the sender.
>
> -----Original Message-----
> From: Jouni Korhonen [mailto:jouni.korhonen@xxxxxxxxxxxx]
> Sent: 24. november 2015 04:30
> To: Yasser Kilde Bajwa <Yasser.Bajwa@xxxxxxxxxxxx>; stds-1904-3-
> tf@xxxxxxxx
> Subject: RE: new seqnum text; was ieee1904_3_D02_20151113_clean-
> seqnum-jik.docx
>
> Yasser,
>
> > -----Original Message-----
> > From: Yasser Kilde Bajwa [mailto:Yasser.Bajwa@xxxxxxxxxxxx]
> > Sent: Monday, November 23, 2015 1:09 AM
> > To: Jouni Korhonen; stds-1904-3-tf@xxxxxxxx
> > Subject: RE: new seqnum text; was ieee1904_3_D02_20151113_clean-
> > seqnum-jik.docx
> >
> > Hi Jouni,
> >
> > I wonder about the reserved field in this proposal. It seems like it
> > is implied that this is a static but configurable value. I just wonder
> > which use this could be put to. The other option could of course be
> > that we always make the upper sequence number counter field fill the
> > remainder of the field. That would essentially just mean that these
> reserved bits always are 0.
> [JiK:] I think it more like just setting an unused space to a known value. And
> setting it to any value is as easy as setting it to zeroes. We might find use for
> that are in the future as well.
> >
> > On another note, shouldn't we just call them the P counter and the Q
> > counter? All the other names, Pmax, PVal etc. seem to make more sense
> > like that. Perhaps even the P (Primary) and S (Secondary) counters.
> [JiK:] Naming proposal sounds ok to me.
>
> - JOuni
> >
> > Best regards
> >
> > Yasser Kilde Bajwa
> > IP Core Product Manager
> > MTI Mobile
> > An MTI Company
> >
> > Krakasvej 17, 3400 Hilleroed, Denmark
> >
> > T: +886 908161200
> > E: Yasser.Bajwa@xxxxxxxxxxxx
> > W: www.mti-mobile.com / www.mtigroup.com
> >
> > -----Original Message-----
> > From: stds-1904-3-tf@xxxxxxxx [mailto:stds-1904-3-tf@xxxxxxxx] On
> > Behalf Of Jouni Korhonen
> > Sent: 21. november 2015 06:39
> > To: stds-1904-3-tf@xxxxxxxx
> > Subject: new seqnum text; was ieee1904_3_D02_20151113_clean-
> seqnum-
> > jik.docx
> >
> > Folks,
> >
> > For the next call some text proposals for the sequence number sub-clause.
> >
> > - Jouni
> > === MICROELECTRONICS TECHNOLOGY INC. === This message (and any
> > attachments) may contain information that is confidential,
> > proprietary, privileged or otherwise protected by law. The message is
> > intended solely for the named addressee (or a person responsible for
> > delivering it to the addressee). If you are not the intended recipient
> > of this message, you are not authorized to read, print, retain, copy
> > or disseminate this message or any part of it. If you have received
> > this message in error, please destroy the message or delete it from
> > your system immediately and notify the sender.
>
> === MICROELECTRONICS TECHNOLOGY INC. ===
> This message (and any attachments) may contain information that is
> confidential, proprietary, privileged or otherwise protected by law. The
> message is intended solely for the named addressee (or a person
> responsible for delivering it to the addressee). If you are not the intended
> recipient of this message, you are not authorized to read, print, retain, copy
> or disseminate this message or any part of it. If you have received this
> message in error, please destroy the message or delete it from your system
> immediately and notify the sender.