[Teas] "Packet Network Slicing using Segment Routing"

"Acee Lindem (acee)" <acee@cisco.com> Mon, 25 March 2019 13:53 UTC

Return-Path: <acee@cisco.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6E881203EF; Mon, 25 Mar 2019 06:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 header.b=Z1h2PLlu; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=F/col4Am
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 rCrsf53ncjid; Mon, 25 Mar 2019 06:53:02 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A90AD12038C; Mon, 25 Mar 2019 06:53:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4439; q=dns/txt; s=iport; t=1553521981; x=1554731581; h=from:to:cc:subject:date:message-id:mime-version; bh=shC1IMM4ASwn2kUU/BqUzklEpCJfMv9LciNB4iwPwok=; b=Z1h2PLlueZR7IyYbcPuJLOKtTCkUsiYmCNYcr35AxJxO09EUC5uSKrEQ BqvdIyckMMEFh1B16OY36P6fzeBB3pNkKruMn5S86brCuCBZ0a1iGiGn5 pyZxv1+1Fol/8fW2RvBkrzUIx7ewQvuAoyL6Kkqb62ymXg/r7Fb8amPux M=;
IronPort-PHdr: =?us-ascii?q?9a23=3AiTKaYRFMpLbierk3jcbmz51GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4w0Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBjyJ/PnRyc7B89FElRi+iLzPA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AYAwD33Jhc/4ENJK1jHAEBAQQBAQc?= =?us-ascii?q?EAQGBZYEPL1ADaHQECyeEDoNHA48qlRqESYJSA1QNAQEshEAZhHsiOBIBAQM?= =?us-ascii?q?BAQkBAwJtHAELhXQdAQE3AREBDD4CBDAnBA6DJwGBEUwDFQGjHwKKFHGBL4J?= =?us-ascii?q?4AQEFgkeCNhiCDAiBL4syF4F/gRABJx+KWDGCJoxzhB+UBwkCkzcZggKJSIg?= =?us-ascii?q?0ixyTKgIEAgQFAg4BAQWBZCGBVnAVZQGCQYIKg26KU3KBKI5+AQE?=
X-IronPort-AV: E=Sophos;i="5.60,269,1549929600"; d="scan'208,217";a="539530534"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Mar 2019 13:52:58 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x2PDqw9C004107 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 25 Mar 2019 13:52:58 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Mar 2019 08:52:58 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Mar 2019 09:52:57 -0400
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 25 Mar 2019 08:52:56 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=shC1IMM4ASwn2kUU/BqUzklEpCJfMv9LciNB4iwPwok=; b=F/col4Am/6VlG9ezWhtLhY8emcezvtlCKRV1yATxE/n5PsIiQ7oUFk0GCCwMfiF2WPw5NygkS+8bAWnjAA2cBppVkPChwiOugWQ5Tt3nNwvXQPnD5kug0fhQK5QzOcmDAMgZpWdw5Tb94Cu7YuOAxmdX/FRBLuair3vManDCjXw=
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com (10.174.112.11) by BN6PR1101MB2145.namprd11.prod.outlook.com (10.174.112.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.15; Mon, 25 Mar 2019 13:52:55 +0000
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::7c15:be1e:a2bd:7e28]) by BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::7c15:be1e:a2bd:7e28%5]) with mapi id 15.20.1730.019; Mon, 25 Mar 2019 13:52:55 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "draft-peng-lsr-network-slicing@ietf.org" <draft-peng-lsr-network-slicing@ietf.org>
CC: "lsr@ietf.org" <lsr@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: "Packet Network Slicing using Segment Routing"
Thread-Index: AQHU4xILek5NKjADBEyPAWo56MO/iA==
Date: Mon, 25 Mar 2019 13:52:54 +0000
Message-ID: <DB700EDA-6ACF-4B17-9B9A-C5C2939F89D7@cisco.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=acee@cisco.com;
x-originating-ip: [2001:420:c0c8:1002::287]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f067457c-fc7a-4b93-cafd-08d6b1292e8e
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BN6PR1101MB2145;
x-ms-traffictypediagnostic: BN6PR1101MB2145:
x-microsoft-antispam-prvs: <BN6PR1101MB21456FEAB45F7411F0B36178C25E0@BN6PR1101MB2145.namprd11.prod.outlook.com>
x-forefront-prvs: 0987ACA2E2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(39860400002)(396003)(376002)(136003)(189003)(199004)(6486002)(478600001)(83716004)(316002)(68736007)(53936002)(476003)(6506007)(9326002)(81166006)(2906002)(2501003)(6436002)(82746002)(6116002)(5640700003)(256004)(54896002)(6512007)(7736002)(6306002)(8936002)(97736004)(6916009)(102836004)(2616005)(106356001)(14454004)(46003)(4326008)(450100002)(105586002)(99286004)(2351001)(486006)(54906003)(71190400001)(86362001)(8676002)(33656002)(81156014)(36756003)(5660300002)(25786009)(71200400001)(4744005)(186003)(440344003)(222603001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR1101MB2145; H:BN6PR1101MB2226.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: U0Y/2tEAQ8nZPM6z2CWFF7ED4S+A7yPjMvG2UYgK1yG0vMNBbIirjTZSQ9EksNt8QhR8DUlTeTPeRLOeIp8J0MVhlJxbIlf31zbggPCLpcxICbBF1zDvAUYh/rjwy5R/thsHVneVk7bR+BZXCPv58pgQqooEFVIJgBMXzNbtZxqKMyQf3+qqH/w08RrOiLuT2FSdL2bwicwExQMPomagwKsKDIgliS4e0o/sPfzUEmRWXrm43bYmuNA/7urveKLWFK/WyltJJfFO+Z8/GbilnU1b+Wtcy2K8GkTAnj0Jm9j7+N7kn19yUqRcq6Re922EL+aiZ94sHqylBMLqwfS7kTwAfz39mCDqd9Nj3MmKbhubAL3QBT4XfT/8s53S+hrOvLuReeI5DI6lYhx/emYPFp9yCL3d7zW6RTpdBMQTDmI=
Content-Type: multipart/alternative; boundary="_000_DB700EDA6ACF4B179B9AC5C2939F89D7ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f067457c-fc7a-4b93-cafd-08d6b1292e8e
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2019 13:52:54.9867 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1101MB2145
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/G4m_0yjXaNAyBx8ZNbeOqrV3tjM>
Subject: [Teas] "Packet Network Slicing using Segment Routing"
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2019 13:53:04 -0000

Hi Authors,

I read this draft on the plane on the way to Prague and I don’t think it belongs in LSR. I believe it belongs in TEAs as it is more about the requirement and framework for TE slicing than it does about adding the Administrative Instance Identifier (AII) to the OSPF and IS-IS TE encodings. We will go forward with the presentation on Thursday with the understanding that LSR will not adopt this work. If it is adopted in TEAS, we can decide whether to proceed with a small LSR draft with just the new AIIs or simply provide review and IANA code points in our registries.

Thanks,
Acee