Re: [Dcrouting] DC Routing requirements draft

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Tue, 23 January 2018 23:58 UTC

Return-Path: <jheitz@cisco.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 68D5112D811 for <dcrouting@ietfa.amsl.com>; Tue, 23 Jan 2018 15:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 SIOCobGZ00Jg for <dcrouting@ietfa.amsl.com>; Tue, 23 Jan 2018 15:58:13 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EBE112D940 for <dcrouting@ietf.org>; Tue, 23 Jan 2018 15:58:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8365; q=dns/txt; s=iport; t=1516751893; x=1517961493; h=from:to:subject:date:message-id:mime-version; bh=wqWBXfhQrfFccoTKqJznUJuQOoMtaxAxHhZMYFdtEbM=; b=djSPzzsghP2GEzsukriUwIB8/EeAN7xKaSqZdPj42cd7rB+Ta8a6GSle qAmVHmaGzKuUvKexzJeoYlCJjz0yzNbrPWvV0sqICkbIi6Y4IQ5ZtLSf4 lxcFqCENL+2DJOievGVABqZS/5PQiV19jS8+f63gF3t459lvqPxIINNDA Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BhAQBHy2da/4YNJK1eGQEBAQEBAQEBAQEBAQcBAQEBAYJKRzFmdC6Neo5lk2yFVIIXCoozVBgBAQEBAQEBAQJrHQuFJAYtXgEIeCYBBBuJSWS1W4pVAQEBAQYBAQEBAQEihEuCFYFXgWiDLoseBaN+ApVSlCyXIwIRGQGBOwEfOT+BEXAVgmiEVo17gRcBAQE
X-IronPort-AV: E=Sophos; i="5.46,403,1511827200"; d="scan'208,217"; a="60181387"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jan 2018 23:58:12 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w0NNwCEH025637 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dcrouting@ietf.org>; Tue, 23 Jan 2018 23:58:12 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 23 Jan 2018 17:58:11 -0600
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1320.000; Tue, 23 Jan 2018 17:58:12 -0600
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: "dcrouting@ietf.org" <dcrouting@ietf.org>
Thread-Topic: Re: DC Routing requirements draft
Thread-Index: AdOUomg9Bp6KcO+RQf69MwGkCayIdQ==
Date: Tue, 23 Jan 2018 23:58:11 +0000
Message-ID: <00db7d5f09b5415ebb42c73e42d2baf6@XCH-ALN-014.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.198.47]
Content-Type: multipart/alternative; boundary="_000_00db7d5f09b5415ebb42c73e42d2baf6XCHALN014ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/FQS518oP3C_WzxJHOm4paV3UnTU>
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, 23 Jan 2018 23:58:15 -0000

Comments on draft-dt-rtgwg-dcrouting-requirements

I'd like to expand on the ZTP requirement.
It is ok to pre-configure devices with items such as a unique identifier, capabilities, port types and so on.
It is not ok to require any of the configured items to depend upon the location of the device in the topology.
In other words, it should be possible to remove a device from any part of the network and put it into another part of the network without any manual configuration. The auto-configuration protocol should recognize the move and reconfigure a moved device.

It should be possible to have multiple networks that are individually auto-configured to be connected to each other in such a way that the auto-configuration of one network does not interfere with the auto-configuration of an adjoining network.

The DC routing protocol should be able to auto-configure and route multiple CLOS networks that are interconnected with a loose data-center-interconnect (DCI) network. The auto-configuration protocol should be able to discover and configure all the datacenters in a DCI as a single network.

The auto-configuration protocol should not require a dedicated (out-of-band) network.

Each device should not be required to know the topology outside of its immediate neighbors. It should be sufficient for a device to know about distant devices in the aggregate. Specific knowledge of certain distant devices should be for special cases only. For example, a network controller is expected to know precise topology information about its domain of control. In particular, each device must not store a complete link state database of the whole network or IP addresses of every leaf in the datacenter.

Thanks,
Jakob