Re: [Dcrouting] DC Routing requirements draft

[Jeff Tantsura <[e-mail]>]

Randy,

please see inline

Cheers,
Jeff

-----Original Message-----
From: Randy Bush <[e-mail]>
Date: Tuesday, October 31, 2017 at 12:43
To: Jeff Tantsura <[e-mail]>
Cc: <[e-mail]>
Subject: Re: [Dcrouting] DC Routing requirements draft

    > The authors have published DC Routing requirements draft
    > (draft-dt-rtgwg-dcrouting-requirements)
    
    usually requirements are motivated/justified; that seems to be missing.
[jeff] to come, we have just started
    
    some would note the lack of is-is and mpls, both known to be used in
    data centers.  hence this is describing needs of a future protocol.  but
    it reads like a laundry list meant to match a protocol product set which
    is yet to be revealed.
[jeff] the intention of the draft is not to call names but to identify set of requirements every proposal (new, or enhancements to an existing protocol) could be compared against in a tangible way, running beauty contest between protocols is not very productive…
    
    > Please note that EDCO group
    > (draft-elkins-routing-brickmortar-topology) input was not included and
    > will have a separate track.
    
    i can not find that draft.  i did find
    draft-elkins-brickmortar-architecture-00.txt which, as we previously
    discussed, does not seem relevant to a data center discussion.
[jeff] the intention here is that it will be relevant, unfortunately, the authors have missed cutoff date to upload new version (still being worked on), the draft will provide description of what it is today and set of requirements as seen by the enterprise DC’s. 
Nalini – please feel free to add your comments.
    
    randy