IETF Logo Mail Archive

Re: [spring] AD Review of draft-ietf-spring-segment-routing-msdc-05

"Alvaro Retana (aretana)" <aretana@cisco.com> Thu, 31 August 2017 21:50 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50183132328; Thu, 31 Aug 2017 14:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 b8Znnw7l-P33; Thu, 31 Aug 2017 14:50:03 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9591321AA; Thu, 31 Aug 2017 14:50:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7194; q=dns/txt; s=iport; t=1504216203; x=1505425803; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1nT3ciyIA2Rv/JuvXvNNmYyaeF6HALv5wy3jNKc3Qro=; b=GwhC2FCRE9zbA6vfSHH+B/xfpcqX409pEibN8SKdj5QXd9W4Q6B6nnDO JBn8GfxX05Z01aGCA/Peo7WWUCi/S/PF8ieTDqhX92H2BNBIv6zMRm0S2 V9ogvWPgGiM9ekrcBehiSTHP5EbaASdPxQG4KUzes9NoG4MHNMFYdcKC3 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DjAABsg6hZ/4UNJK1dGQEBAQEBAQEBAQEBBwEBAQEBgm9rZIEVB44QkB6BT4hbiDCFPoIShUcCGoN1PxgBAgEBAQEBAQFrKIUZBiNWEAIBCBItAwICAh8RFAMOAgQOBYlNTAMVr3+CJyeHEg2EGgEBAQEBAQEBAQEBAQEBAQEBAQEBAR2DKoICgU6CDguCcoJXhTEwgjEFmDGIAjwCj1mEdoIThWeKdIxOiXYBHziBDXcVWwGHCHaJS4EPAQEB
X-IronPort-AV: E=Sophos;i="5.41,455,1498521600"; d="scan'208,217";a="293547514"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 Aug 2017 21:50:02 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v7VLo25Y017885 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 31 Aug 2017 21:50:02 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 31 Aug 2017 16:50:01 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1263.000; Thu, 31 Aug 2017 16:50:01 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Robert Raszuk <robert@raszuk.net>
CC: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>, "draft-ietf-spring-segment-routing-msdc@ietf.org" <draft-ietf-spring-segment-routing-msdc@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] AD Review of draft-ietf-spring-segment-routing-msdc-05
Thread-Index: AQHTIp4/lbjU1rcIckyJLsBqY8MRC6Ke8DCA
Date: Thu, 31 Aug 2017 21:50:01 +0000
Message-ID: <DEE34F25-AA1E-4916-8ED6-F6D66AAF3F9F@cisco.com>
References: <3822F955-321A-4B53-AAB6-1628811E32B8@cisco.com> <CA+b+ERn9UOfZv1Dv0Z6szCwKLb+ub8tP5_dKiJ8gxi_2cENM9Q@mail.gmail.com> <CA+b+ERmeQx2bKaT-gQMDcuLyMvo3gKvKoEQnDJDAqAsaUsvo=g@mail.gmail.com>
In-Reply-To: <CA+b+ERmeQx2bKaT-gQMDcuLyMvo3gKvKoEQnDJDAqAsaUsvo=g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.25.0.170815
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.225.239]
Content-Type: multipart/alternative; boundary="_000_DEE34F25AA1E49168ED6F6D66AAF3F9Fciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/tRZ2ETQMFaEkuEHoDjqBVuAn2hc>
Subject: Re: [spring] AD Review of draft-ietf-spring-segment-routing-msdc-05
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2017 21:50:05 -0000

Robert:

I understand.

My main point is that the spring architecture document should clearly make that clear.  Right now, it is really easy to interpret the SR domain ending at the routing edge (not the hosts).  Also, the architecture is the right place to have this discussion.

Thanks!

Alvaro.

On 8/31/17, 3:15 PM, "rraszuk@gmail.com<mailto:rraszuk@gmail.com> on behalf of Robert Raszuk" <rraszuk@gmail.com<mailto:rraszuk@gmail.com> on behalf of robert@raszuk.net<mailto:robert@raszuk.net>> wrote:

Please observe that in overlay networking it is reall hosts how can compute required path or exit gateway and apply it to packets. Think about Contrail or Nuage.

It is also not about "programming hosts to apply a header" it is hosts itself determine based on the local application needs what the header is. This is naturally applicable to msdc.

The times where the network nodes only do networking are long time gone.

v2.23.0 | Report a Bug | By Email