| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
I agree with everyone's comments below. Trying to define what "minimal augmentation" is will be difficult to agree.
And, since we are in this subject, I will take the opportunity to say that I've been worried precisely about the lack of specificity of this objective.
I'm not advocating that we change it, but it seems to me that this requirement is purely a matter of personal interpretation (e.g.,someone might argue that "this XYZ change to MPCP IS a minimal change" while someone else might say "this XYZ change IS
NOT a minimal change". And, quite frankly, what specifically worries me is that this lack of specificity might open up the opportunity for someone to leverage it as a reason for not accepting a proposal. (I know… who would do that! ;-/)
I know that all of the above expresses my opinion but does not help the discussion one iota, but I wonder if I could hear opinions as to what would be considered to NOT be "minimal augmentation". Could someone volunteer examples of changes to MPCP that
would NOT be "minimal augmentation"?
Jorge
From: Marek Hajduczenia <marek.hajduczenia@xxxxxxxxx>
Reply-To: Marek Hajduczenia <marek.hajduczenia@xxxxxxxxx> Date: Friday, August 10, 2012 8:15 AM To: EPoC Study Group <STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx> Subject: Re: [802.3_EPOC] Minimal MPCP Augmentation My 0.02 eurocents are quite similar – we will only be able to see what augmentation is needed when we see detailed proposals for the
PHY, operation of individual layers and EPoC as a whole. Trying to nail it down right now is hardly a good use of everybody’s time. I’d have this discussion once (1) we know how PHY operates to meet the objectives and (2) when and if we are certain that existing
MPCP does not work properly for this PHY. Marek From: Avi Kliger [mailto:akliger@xxxxxxxxxxxx]
Matt, I like your interpretation. This was my understanding as well. Only make the minimal necessary changes required to meet the objectives.
Thanks Avi From: Matthew Schmitt
[mailto:m.schmitt@xxxxxxxxxxxxx] Hesham, My personal opinion is that we're unlikely to come up with any sort of definition in advance that we can all agree on, particularly when it is
a theoretical exercise. Rather, I suspect that what will ultimately happen is that we'll need to look at specific individual cases and then decide as a group whether or not we feel a particular change meets that definition. Put another way, I don't know
that we can or should try to decide a strict definition now, but rather that we should wait until we have specific proposals and evaluate them with this in mind. Additionally, I have always looked at that statement as "the minimal necessary" augmentation to achieve our objectives. Admittedly that's not
precisely what it says, but that's how I've viewed that statement, and one way in which I believe you could interpret it. Because in the end I think that's exactly what we need to do: make those changes that are necessary to enable our objectives, while showing
restraint so that we don't make changes that are absolutely necessary. My $0.02 worth – I will be interested in hearing others' thoughts. Thanks. Matt From:Hesham ElBakoury <Hesham.ElBakoury@xxxxxxxxxx> Through the discussions we had so far I do not see a common agreement on the definition of “minimal augmentation” to MPCP. For example which one of the following MPCP changes are considered “Minimal” augmentation to MPCP and why:
1.
Defining a new MPCP message. 2.
Adding a new field to an existing MPCP message. 3.
Change the interpretation/definition of existing field(s) in MPCP message. 4.
Using reserved/unused fields in existing messages. 5.
…. Comments are welcome. Thanks Hesham <="" p=""> <="" p="">
|