[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [PWE3] Inter-op is not necessary



Here is my (re)vote:

Q1. Are you in favor of moving MS-LDP forward as WG draft?
A1. Yes. Please note that the CR-LDP issue is a NONissue.
    First, the decision to terminate work on CR-LDP was
    purely an MPLS WG decision, and has no impact on PWE.
    Second, what is being proposed is NOT CR-LDP,
    but rather a different augmentation of LDP.

Q2. Are you against moving MS-LDP forward?
A2. No. (Isn't the answer to this question always strongly
anticorrelated to A1?)

Q3. Are you in favor of moving MS-RSVP forward as WG draft?
A3. No, as I do not see any advantage at this time.
    although I understand its advantages.    
    But I do not object to the authors continuing to work on this
    and presenting their results to the WG.

Q4. Are you against moving MS-RSVP forward?
A4. Not strongly, but once again I believe this answer MUST strongly
    antocorrelate to A3.

Q5. Are you in favor of a single solution?
A5. Absolutely. We do not want to have to build signaling interworking
functions.
    It is bad enough that for historical reasons we have so many
protocols
    so many interworking functions,
    why would we want to knowingly recreate this situation for new
protocols ?
    

Aside: in another standardization in which I was involved,
namely modem DSP design, we had a similar situation of two alternative
approaches, each of which was stronger at one point in time
and later weaker. The QAM approach won out in V.34 just as RSVP-TE
one the first round here. Then in ADSL the DMT approach succeeded
(think LDP).
The final battle was for VDSL, and both sides dragged the discussion
on for years (claiming that more data was needed in order to decide), 
to the detriment of the community and end-users.
The final result was DMT plus a weak allowance of QAM.

I would hope that we don't drag the discussions on here for years,
and would strongly suggest not allowing a secondary approach,
which merely confuses and segments the community. 


Y(J)S

_______________________________________________
pwe3 mailing list
pwe3 at ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3