Issue 7.1: Mandatory-to-implement criteria

[Andy Bierman <abierman@cisco.com>]

Hi,

From the issue list:

7.1) Need to compile a list of criteria then prioritize the list.  

  Proposal: 
    - reach stable snapshot state with netconf drafts, without
      making the mandatory-to-implement choice yet
    - allow some developers to implement the stable snapshot
      for 1-3 of the application mappings
    - bugfix the drafts in the meantime, as errors are discovered
    - in 4-6 months, 
      - developers will give the WG implementation reports
      - based on this implementation experience, the WG will 
        choose a mandatory-to-implement
      - the WG will choose a mandatory-to-implement within 4-6 months
        even if implementation reports are not available

I believe this proposal is too vendor-centric.  I suspect
SSH and BEEP implementations will take roughly the same 
amount of effort anyway, so implementation experience will 
not provide compelling evidence.

Operator preference -- a bias towards deployment difficulty
rather than implementation difficulty -- is more important 
criteria for picking the mandatory mapping.  Most operators
who have stated an opinion prefer SSH. All of them want
the protocol to work the same no matter which application
mapping is used.  I don't think we need to wait 6 months
to determine the operator consensus.  As a vendor that
is likely to end up supporting 2 if not all 3 mappings, 
I don't need 6 months to decide either.

I would like the WG to comment on this issue, state
your preferred solution and why:

  a - pick SSH as the mandatory mapping
  b - pick BEEP as the mandatory mapping
  c - pick SOAP/HTTP as the mandatory mapping
  d - accept the 7.1 proposal
  e - accept the 7.1 proposal, but consider deployment
      issues, not just implementation issues 
  f - create a requirements list and evaluate all
      3 drafts against this list

Andy

  



--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>