IETF Logo Mail Archive

Re: [spring] Updating the SPRING WG Charter

<Ruediger.Geib@telekom.de> Tue, 19 June 2018 11:46 UTC

Return-Path: <Ruediger.Geib@telekom.de>
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 E10511277C8 for <spring@ietfa.amsl.com>; Tue, 19 Jun 2018 04:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 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_MED=-2.3, T_DKIMWL_WL_HIGH=-0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de header.b=s9UREaJt; dkim=pass (1024-bit key) header.d=telekom.onmicrosoft.de header.b=TDsTaAub
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 xnwiby6u-HZA for <spring@ietfa.amsl.com>; Tue, 19 Jun 2018 04:46:27 -0700 (PDT)
Received: from mailout34.telekom.de (MAILOUT34.telekom.de [194.25.225.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1C69130DDC for <spring@ietf.org>; Tue, 19 Jun 2018 04:46:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1529408786; x=1560944786; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ZCULILVc1IF9dVVzxzxb/QpsfxQ3EfbWyghW+zlRHsw=; b=s9UREaJtfIdGXIQ3Dfbu5EcpAQirWYFZJXOpdUXmw/X1vRWHSf+owFp0 4/N+/aUYc6E4zDZ3mY4fVQfYUEP5z2jp28cb80sy2251093Z/UI2/i0OM 201JB6UuIkitG/3Ras9oRHT9qNBrs/t/kNEc4s+RDwvw0fTJJbZNBRuXN 8y4sxmnBdppTpQai0pZU9rMrMbDlUCqTFG1QVhlLSyuQ7xUztosuDY0MB cKthx2C/w1k5n0tLJl6vXBcE+iVu7RfJoTwOD3o3P5iAYF1hBzwKania6 j9vlTx55nyF2/UQip/MChrdWt7p2Gse3T3yPJWXFOchdH+s5jElM+Y+vZ A==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jun 2018 13:46:23 +0200
X-IronPort-AV: E=Sophos; i="5.48,405,1517871600"; d="scan'208,217"; a="68530886"
Received: from he105661.emea1.cds.t-internal.com ([10.169.119.57]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 19 Jun 2018 13:46:23 +0200
Received: from HE105684.EMEA1.cds.t-internal.com (10.169.119.46) by HE105661.emea1.cds.t-internal.com (10.169.119.57) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 19 Jun 2018 13:46:23 +0200
Received: from HE104162.emea1.cds.t-internal.com (10.171.40.37) by HE105684.EMEA1.cds.t-internal.com (10.169.119.46) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Tue, 19 Jun 2018 13:46:23 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.20) by O365mail04.telekom.de (172.30.0.231) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 19 Jun 2018 13:44:48 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.onmicrosoft.de; s=selector1-telekom-onmicrosoft-de; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZCULILVc1IF9dVVzxzxb/QpsfxQ3EfbWyghW+zlRHsw=; b=TDsTaAubZPWyFhZmbHtl9cY7PtQNu7JucLT/+ZxsXwYfhsMpo8HuUXYoUp5I2GYDWQgm5ubN9iIVeU+szLUnnFsug2C8iVAIC0clui6Qy2u0B9bLOLD2yjBYm94Da8kryH2/Mfvmo/U3uJ6rT+3LiZzhYe8Pbhc4fNbwltNKhHY=
Received: from FRAPR01MB0737.DEUPRD01.PROD.OUTLOOK.DE (10.158.134.150) by FRAPR01MB0737.DEUPRD01.PROD.OUTLOOK.DE (10.158.134.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.14; Tue, 19 Jun 2018 11:46:22 +0000
Received: from FRAPR01MB0737.DEUPRD01.PROD.OUTLOOK.DE ([fe80::6123:4349:c56b:bd5a]) by FRAPR01MB0737.DEUPRD01.PROD.OUTLOOK.DE ([fe80::6123:4349:c56b:bd5a%2]) with mapi id 15.20.0863.016; Tue, 19 Jun 2018 11:46:22 +0000
From: Ruediger.Geib@telekom.de
To: stewart.bryant@gmail.com
CC: spring@ietf.org
Thread-Topic: [spring] Updating the SPRING WG Charter
Thread-Index: AQHUB79Qb2WE4BtuQ0iRzbs6VN00gqRndISA
Date: Tue, 19 Jun 2018 11:46:22 +0000
Message-ID: <FRAPR01MB073780BE87612487CE1284329C700@FRAPR01MB0737.DEUPRD01.PROD.OUTLOOK.DE>
References: <CAHd-QWt+nmQz_R7kE2oeHa2cD88+ndSkpiv56WSFJfHH3PzxRQ@mail.gmail.com> <bac92e67-ef32-8a4a-1f55-a0d43d5004ae@gmail.com>
In-Reply-To: <bac92e67-ef32-8a4a-1f55-a0d43d5004ae@gmail.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Ruediger.Geib@telekom.de;
x-originating-ip: [164.19.3.142]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; FRAPR01MB0737; 7:Sj/X1FEDaBqjf4MHH+a+aHbEqd8A6bH8Odgwgy+FadN8LZFw1ZCEcage0SVNec9ECFsE0XF3k0s3ydG0Wx1MZ7TIuFrsEUYbP553pfrnEqZXcDZgxm386raStGVLJNfwBmsB9dpbJSgxUFl2FYZGKy7Oqjxln8a31OqsJDVWz7t0k6YHvAjYkSU78HhGVM3B6rW6sdD0cMb0DlPAK+PZYLzWnzOOgfg8G7kn8uhLVwCDF2wOqKK2N4sWvoEnIFLM
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: ec9a28e9-20d7-49d2-8187-08d5d5da47b1
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(711020)(2017052603328)(7153060)(7193020); SRVR:FRAPR01MB0737;
x-ms-traffictypediagnostic: FRAPR01MB0737:
x-microsoft-antispam-prvs: <FRAPR01MB0737A2CC312A0655519643849C700@FRAPR01MB0737.DEUPRD01.PROD.OUTLOOK.DE>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231254)(944501410)(52105095)(3002001)(10201501046)(149027)(150027)(6041310)(20161123560045)(20161123562045)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:FRAPR01MB0737; BCL:0; PCL:0; RULEID:; SRVR:FRAPR01MB0737;
x-forefront-prvs: 07083FF734
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(346002)(376002)(39860400002)(366004)(396003)(37854004)(199004)(189003)(51444003)(6916009)(55016002)(52396003)(7696005)(446003)(86362001)(6306002)(54896002)(3660700001)(186003)(53546011)(68736007)(9686003)(66066001)(11346002)(5250100002)(85182001)(26005)(7736002)(76176011)(97736004)(102836004)(75402003)(478600001)(476003)(72206003)(74482002)(2900100001)(6116002)(3846002)(105586002)(106356001)(8676002)(53936002)(8936002)(85202003)(486006)(14454004)(39060400002)(33656002)(5660300001)(316002)(4326008)(81166006)(81156014)(790700001)(3280700002)(2906002)(777600001)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0737; H:FRAPR01MB0737.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-microsoft-antispam-message-info: FLE4cXi+Le+hyo8bUFFBMYhclXGqoIiDktQkD17KgZhu93B9bCNzkoaSb1AWb7DNZ79m3uLSv5QNz77ELjWlR6k+7Ar2uNEUn4K7iz7ItO68IxH1eW2QJw9gQ279rusWROzk8NxmPdLGBFAO6t/zT6AoTTqzVYgSY2/UunIfUpOUx7S6dRJhwbIqAFcfjjyLduh8cPXkK1n9XXWz2lTmfdwQA0p757dnwxkYxRqXSoy8XwwiaETWzeRb4eWgSiTYAdtnwgowxU6e1q/di3b/C9ORFlmf6zJWahSj0ldHTc3N6iUTsIn3SMyjNXLNEClX
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_FRAPR01MB073780BE87612487CE1284329C700FRAPR01MB0737DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ec9a28e9-20d7-49d2-8187-08d5d5da47b1
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jun 2018 11:46:22.4101 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0737
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/UeViNK8l6j-P4y1gHBn2UpxrpzQ>
Subject: Re: [spring] Updating the SPRING WG Charter
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <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: Tue, 19 Jun 2018 11:46:32 -0000

There’s no objection against policies installed at ingress interfaces to an SR domain. Rob correctly states, that the SR architecture does not require per path state at transit nodes. And that’s good and correct. I’d like to see the number of signaling protocols in the SR core network being reduced as compared with today’s MPLS network, not increased.

There’s RSVP-TE for MPLS, which can be deployed for services requiring per path state at transit nodes.

Regards,

Ruediger

Von: spring [mailto:spring-bounces@ietf.org] Im Auftrag von Stewart Bryant
Gesendet: Dienstag, 19. Juni 2018 13:19
An: Rob Shakir <robjs=40google.com@dmarc.ietf.org>; SPRING WG List <spring@ietf.org>
Betreff: Re: [spring] Updating the SPRING WG Charter




On 01/06/2018 17:05, Rob Shakir wrote:
The SPRING WG defines procedures that allow a node to steer a packet through an
SR Policy instantiated as an ordered list of instructions called segments and
without the need for per-path state information to be held at transit nodes.

I am not sure where the line gets drawn with the per-path state statement. If I introduce a
binding-SID to allow the creation of a path, have I introduced per-path state or not? In practise
a management entity will choose between the infinity of possible binding-SIDs by considering
the need to create specific paths and I would imagine that many will be instantiated just-in-time.

I think that the key point is that the ingress creates the path by using SIDs to create
a concatenation of paths, policies and resources. However it could be argued that
as soon as we introduced Binding SIDs we introduced per-path state. I think we might
be best served by deleting the text I have highlighted.

- Stewart

v2.23.0 | Report a Bug | By Email