IETF Logo Mail Archive

[spring] Can features described by draft-ietf-spring-sr-service-programming-01 be supported by draft-ietf-spring-srv6-network-programming-08?

Linda Dunbar <linda.dunbar@futurewei.com> Fri, 17 January 2020 00:31 UTC

Return-Path: <linda.dunbar@futurewei.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 0C04D120099; Thu, 16 Jan 2020 16:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 4aQjxDmK-Dpw; Thu, 16 Jan 2020 16:31:21 -0800 (PST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2096.outbound.protection.outlook.com [40.107.220.96]) (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 3AEA1120059; Thu, 16 Jan 2020 16:31:18 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UxYt4lK1W5jHosJqANLlT25s3NnUcdGzs++CzM3rfAyokZ5H0L5fSS8WwYotRHZX8gaz9H2a4Ny414IlpqNsiHcKdo9ACu0hsl0c8UyDmsX6S26RH/TIREu+EyvHrONP5WhEED+ir2Jh4N2xN96pN7nrDfLCsaL+6fma3DF5alpdpydh46S+HZpl5szXhkQlVuU8YjCCQj/6GoRsiE9v+8XA6zj2OY5X4XmFPsuiSf7U083qk04odkCvmmE62w6YT7ogX55ArbNoz9wfB6rUjx4VtPiKgitBwNLyqGPtni/i095I3PvlFcxVbCMPWjbAdjGDiTCh2Sl9vDRHA7oIpA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GGZzJKQsH/wG6MImhInP+nE2D8BiF6HOqKOlfJ5xy78=; b=ZIAzvyKwfDs+IhsYv26YU1MEviliSpb+eiundXMmHnLmcr8Cvj7CKZwvfnuTaFXIbIsTbv7JTFpSGIUV6nLCE41ZHXyaR0/x5+gNvyUjillJapoK8DQBBR9/Oq0J6M+77P6pNjY6S6cZpLBwIerRFI7R8PKIh6i4uCA4Ys776GvGGeIvO31xBRfCqL2l+oEwn4RBoFkaCNtMpPA79ToMwVCY5g+tNj6h23MklSeH2lPYOzBlpt3mSShSyboPgAznqGJ+vL2kQ5gVQx+anDbhQ0tUyRCS+4W4d8XfJxQP+LMUtwug2+LNWpyItHkiRPh+2RorlV38XjcAojZZHCAbIQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GGZzJKQsH/wG6MImhInP+nE2D8BiF6HOqKOlfJ5xy78=; b=ccCNv1jeb0St/j7+cXqD7J7BGL/ymZtMiHgSpHrmJQD6p9TRrAUGpkwDK4etnH84mFahH/BQ1CWZguusP/iy1oS33qpbygaRTEs8wf9MGkzQVkoVIM9ZTR2REniF+kn04CdjCsO3boJiCa5K1exuy9qeGX4rwAsAPJbTy8idBQA=
Received: from MWHPR13MB1056.namprd13.prod.outlook.com (10.169.201.148) by MWHPR13MB1469.namprd13.prod.outlook.com (10.175.139.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.5; Fri, 17 Jan 2020 00:31:14 +0000
Received: from MWHPR13MB1056.namprd13.prod.outlook.com ([fe80::925:4f4e:99f0:4051]) by MWHPR13MB1056.namprd13.prod.outlook.com ([fe80::925:4f4e:99f0:4051%10]) with mapi id 15.20.2644.023; Fri, 17 Jan 2020 00:31:14 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "draft-ietf-spring-sr-service-programming@ietf.org" <draft-ietf-spring-sr-service-programming@ietf.org>
CC: SPRING WG <spring@ietf.org>
Thread-Topic: Can features described by draft-ietf-spring-sr-service-programming-01 be supported by draft-ietf-spring-srv6-network-programming-08?
Thread-Index: AdXMzV3AedIt2NcRRW+YSQU/nUYFcQ==
Date: Fri, 17 Jan 2020 00:31:14 +0000
Message-ID: <MWHPR13MB10564BB4AE8D7316009439FB85310@MWHPR13MB1056.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=linda.dunbar@futurewei.com;
x-originating-ip: [12.111.81.71]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7a4020d5-7dd3-4076-ef6c-08d79ae48f7e
x-ms-traffictypediagnostic: MWHPR13MB1469:
x-microsoft-antispam-prvs: <MWHPR13MB1469CC96425767D6595C88CB85310@MWHPR13MB1469.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 0285201563
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39840400004)(346002)(376002)(396003)(366004)(136003)(189003)(199004)(71200400001)(33656002)(4326008)(9686003)(450100002)(55016002)(5660300002)(52536014)(76116006)(66446008)(66556008)(66476007)(478600001)(64756008)(66946007)(4744005)(6916009)(26005)(186003)(86362001)(2906002)(8936002)(81156014)(44832011)(8676002)(81166006)(316002)(7696005)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR13MB1469; H:MWHPR13MB1056.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: QML6lcls03BhyU9ZrF12uIg9wYUbHjYiPMiWrfBsjj3307n50rr2PmEXLlaMpaBaFxVpHFEP3iJzXRVCjvVPgHliMJxHhG8+8GrR3WB+qnJPUrEFzMqbmRJKInMdLJiGuEFTtqggaD3tW6s0GW5Py6H8kNT/Neb7qhyoyLJgar/rR1n49fgg8mNsZca6cUjZfrTUvGXpHlrOJP51J/IOplDIB5YnBt98TRzRtWCTYkHA/DLMN4l/JysNdvbdvrynEy6nKgzSwDHwvpPSmkBKA0tHQ4jO0vsAnoKAPnc5PZiAg6DRqImmE6GRM1qEWJaZRC606BuP+HCmvQyrLmucOCChC0yVQuJ9VXl8EcQrwNPnodsnJHI2vx34q5Arb7W0FPIcdXDj8M93WuVc3s6+wYy9hyMspK7wz3ytTsyrqRtZ8vlYJLE2wPD51XOyJ2Mm
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR13MB10564BB4AE8D7316009439FB85310MWHPR13MB1056namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7a4020d5-7dd3-4076-ef6c-08d79ae48f7e
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jan 2020 00:31:14.4177 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: wertNWELf39ZaMN9ntZiibHJabdmcLsgoVhMfJzTJZdAR9QQFP0ppYCUH7b2ANTLtfMfA+i7qLuwrhdG2kXDpw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR13MB1469
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Q7I-RJUtTNMVCW9babUdF9fiBJ4>
Subject: [spring] Can features described by draft-ietf-spring-sr-service-programming-01 be supported by draft-ietf-spring-srv6-network-programming-08?
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 17 Jan 2020 00:31:23 -0000

Authors of draft-ietf-spring-sr-service-programming-01:

"draft-ietf-spring-sr-service-programming" specifies Service SIDs to be embedded into the SID list. Does it make the SID list even longer? For example,  if a packet needs to be steered through the network by 3 SIDs (S1, S2, S3), Service SIDs will be the additional SIDs to be added to the packet header?

It seems straight forward for draft-ietf-spring-srv6-network-programming to add an instruction to forward the packet to a specific service Function.  Why not using draft-ietf-spring-srv6-network-programming to steer packets to specific service functions?
What features specified by draft-ietf-spring-sr-service-programming that can't be achieved by draft-ietf-spring-srv6-network-programming?

Some minor questions:  What is the ENH in Section 6.1.2? You have ENH = 59, ENH = 4,  Are  you talking the Ethernet frames being encapsulated by SRH header?
The inner payload are IP frames, aren't they?

Thank you very much,

Linda Dunbar

v2.23.0 | Report a Bug | By Email