IETF Logo Mail Archive

Re: [Dcrouting] DC Routing requirements draft

Randy Bush <randy@psg.com> Tue, 31 October 2017 19:43 UTC

Return-Path: <randy@psg.com>
X-Original-To: dcrouting@ietfa.amsl.com
Delivered-To: dcrouting@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEEB913F5D8 for <dcrouting@ietfa.amsl.com>; Tue, 31 Oct 2017 12:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vx5dEgsXGPSN for <dcrouting@ietfa.amsl.com>; Tue, 31 Oct 2017 12:43:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB8BF138D8F for <dcrouting@ietf.org>; Tue, 31 Oct 2017 12:43:56 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1e9cS3-000526-0o; Tue, 31 Oct 2017 19:43:55 +0000
Date: Tue, 31 Oct 2017 19:43:53 +0000
Message-ID: <m2vaiv2jd2.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: dcrouting@ietf.org
In-Reply-To: <56F12355-DBF1-47C8-B7F7-C057DC40F1B0@gmail.com>
References: <56F12355-DBF1-47C8-B7F7-C057DC40F1B0@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/zx4LPKe2gjhqIvaXQcnuAR7qd0w>
Subject: Re: [Dcrouting] DC Routing requirements draft
X-BeenThere: dcrouting@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Routing in the Data Center: discussions about problems, requirements and potential solutions." <dcrouting.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrouting>, <mailto:dcrouting-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrouting/>
List-Post: <mailto:dcrouting@ietf.org>
List-Help: <mailto:dcrouting-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrouting>, <mailto:dcrouting-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 19:43:58 -0000

> The authors have published DC Routing requirements draft
> (draft-dt-rtgwg-dcrouting-requirements)

usually requirements are motivated/justified; that seems to be missing.

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.

> 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.

randy

v2.23.0 | Report a Bug | By Email