Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt

"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com> Tue, 08 October 2019 07:02 UTC

Return-Path: <pcamaril@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC56612000F; Tue, 8 Oct 2019 00:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, 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 header.b=CCL/QevV; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=V2iVZa66
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 nj4cz5TtCxwN; Tue, 8 Oct 2019 00:02:48 -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 A88861200B5; Tue, 8 Oct 2019 00:02:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41341; q=dns/txt; s=iport; t=1570518167; x=1571727767; h=from:to:cc:subject:date:message-id:mime-version; bh=yqL36qvbVH7gSJ2vqPEgn6Ht/d+fdY4OoXZ8ofccaYc=; b=CCL/QevVK8OklziFp+ZMPgRVYZVtRgkHlthg1QtAt+sIAwcepVLA5pkY 7pW63AYw8/EmhJpZlMM2I1okEUPReVyKQg1zN7lcCV16h/Ixz36k4DWX9 PNUwBfj15rxIpVprMcHY1TMl87l1ctlq4iK12uL+YwzS6nNELuWLE4swQ A=;
IronPort-PHdr: 9a23:hlv9UBFLsxl3k6nxrnk4qp1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+eebhZikzBsVGfFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BKAABhNJxd/5tdJa1mHAEBAQQBAQwEAQGBUwcBAQsBgRsvKScDbVYgBAsqCoQZg0cDhFiFcoJcgmOHBo4TgS4UgRADUAQJAQEBDAEBGAEMCAIBAYN7RQIXgk0jNAkOAgMJAQEEAQEBAgEFBG2FLQyFSwEBAQQBARARChMBASwLAQsGAQgRAwECIQEGAwIEJQsUCQoEAQ0FIoMAAYEdTQMdAQ6iZgKBOIhhdYEygn0BAQWBOAIOQYJ/GIIXCYE0AYUVhngYgUA/gTgfgkw+ghpHAQECAQEWgRQBEgEHLwgBFgiCTzKCJo9thTWJCyGOBC1BCoIihwmKCYQGG4I6coZceoVEiHmMeoEygT+GYoINjwQCBAIEBQIOAQEFgVI5Z3FwFRohKgGCQQlHEBSBT4EnAQiCQ4UUhT90AQGBJ41+gSIBgSIBAQ
X-IronPort-AV: E=Sophos;i="5.67,269,1566864000"; d="scan'208,217";a="643726263"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Oct 2019 07:02:46 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x9872kMa010299 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 8 Oct 2019 07:02:46 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 8 Oct 2019 02:02:45 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 8 Oct 2019 03:02:44 -0400
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 8 Oct 2019 03:02:44 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jZPL/akV7t/FdhxCQ8kWsMlK8X2NVTlsI3tq3tO0y/mvWyH5AMFGKwCSWJ3qtKPXHpE2vQPOYIKJQAx0Tt58hvAsfD3jNByCiMNFA7KbxGpGQOwWxYUaojOeV2mvBOmHhJq2U7+bkyxvjSFNXpavZbKoMtTF5JE6CF4qZHGQYD0G+dT+kqeCDFcshlyxSTZZlhxH/J90LS0vIhGpwZKQdRSxjxuegPI0lmc4pFdkvn/QWR6FP3C7QiTLpCab/SjSjzFYj4gxq33luM/kzvZwQCBrfDS6U3CQn+o+OpFPUQNQ0DpZyFDk8EXcbgrVjpeg0Qf3bMOtXCGBWgunSod0ZQ==
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=yqL36qvbVH7gSJ2vqPEgn6Ht/d+fdY4OoXZ8ofccaYc=; b=OIG0CFB6x0Qv8jEykDCPySmGF1C2zrim+xUPQd3240l+zZAY1s1+dOHQopnNuA/L2Z2kY908QPTwpUYDL1VA/eYt20KbdQZiXYxYRgcYFRrBjuIzSkX1DqtFQZ3u946Hsk1VLDB0sOHDPOh3051PFb/oXYUB4Ze7H2EA10Q0+iHWjUIEFmAkWCTNPVnl2/0LKH2hu+g0unkkm/Pb8FeKjNseCfFzvqZlLcreZBiP+fgjwAvMOD9wZlasEx21sbpRzzhcA+P3Of7V0s1pvJ3zQ7zD9zr3PGWWl5mqUFhhvG9OR1ga63dXCuYQuLxCLoYqKZAaPXgN2rF3HRInR6n8fg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yqL36qvbVH7gSJ2vqPEgn6Ht/d+fdY4OoXZ8ofccaYc=; b=V2iVZa66o+5WW/TL/EwT+1bAs66XOyJzB55u27AbzmOFsUBJlztNiXJuelXa9svg4pHAaEnD5YT3WeN6wZXiOUX3oOR+gzwowRoQn7eYjBQ7da61tyBKViNb/ejGiBBCw+zEXObmSrIo8EdUIjDkgKHHRYrpgHzZucz55gOphKY=
Received: from MN2PR11MB4094.namprd11.prod.outlook.com (10.255.180.202) by MN2PR11MB4031.namprd11.prod.outlook.com (10.255.180.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2327.24; Tue, 8 Oct 2019 07:02:43 +0000
Received: from MN2PR11MB4094.namprd11.prod.outlook.com ([fe80::5de0:4167:1f9e:d7e2]) by MN2PR11MB4094.namprd11.prod.outlook.com ([fe80::5de0:4167:1f9e:d7e2%5]) with mapi id 15.20.2347.016; Tue, 8 Oct 2019 07:02:43 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: li zhenqiang <li_zhenqiang@hotmail.com>, "spring@ietf.org" <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
CC: draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
Thread-Topic: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
Thread-Index: AQHVfaZhtpPHFDkEtkCL+viyf1d3Qw==
Date: Tue, 08 Oct 2019 07:02:42 +0000
Message-ID: <6CBA3B80-D7B6-485A-BBA5-08E0604520AC@cisco.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pcamaril@cisco.com;
x-originating-ip: [173.38.220.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5453b107-1c7c-4e6d-c6df-08d74bbd8405
x-ms-traffictypediagnostic: MN2PR11MB4031:
x-microsoft-antispam-prvs: <MN2PR11MB40314897839947C135C6EF2FC99A0@MN2PR11MB4031.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01842C458A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(346002)(376002)(39860400002)(136003)(13464003)(189003)(199004)(53754006)(110136005)(25786009)(45080400002)(14454004)(966005)(256004)(7736002)(14444005)(478600001)(66066001)(71190400001)(71200400001)(316002)(33656002)(6512007)(6306002)(6486002)(2616005)(236005)(66446008)(229853002)(476003)(91956017)(54896002)(486006)(64756008)(66946007)(66556008)(8676002)(99286004)(186003)(36756003)(8936002)(5660300002)(2906002)(81156014)(2501003)(66574012)(81166006)(790700001)(6116002)(4326008)(26005)(6506007)(6246003)(86362001)(102836004)(53546011)(2201001)(3846002)(66476007)(76116006)(6436002)(574754004)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4031; H:MN2PR11MB4094.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: BCL:0;
x-microsoft-antispam-message-info: y+bOIwsij/bca2dYYGn/D+D9vaD6wmkXPD6zXfS3A2jtLWZsqtGxhf+bsqiGdh8KGD3RkEdE1OzFcm3TfdXp+qBHKQ5RQSZ8XVqqhrkOKbzCLu5+RLyvCSdYIe24Bn0n7qBzKrGtHD0Eeyav9Re4zFkyjPUIAsguh8ge/CgcAnqwptXCM+V5rUA89uRX87HLRVTgCMpxeS6ctXGCSxvy1HE93c3i0uwdpt17RmOLPbSVHfFYPAWnFBXOgha+7NgFJzI+FAiwKwFaBJD2qvzuAIYLrHkj2R08PYvnb6yGS1EBUGq6ucwQdY5B9OJW9NYuqadAUBwXcCaw4HFAc1+ILf2R45fHiXzLvxCx3gvOS/xxXKC9wctEdxN5MIud1gHW8oeDgA3QgryzB7TW/V0zN7Zw6ZPGWJaheRxBNsa8cOU=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_6CBA3B80D7B6485ABBA508E0604520ACciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5453b107-1c7c-4e6d-c6df-08d74bbd8405
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2019 07:02:43.0648 (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-CrossTenant-userprincipalname: LnvqN+O+ykBuLNTJ1XhMYKCwjTMOf1b13nhnlEg7hEcl+SOut8XTDQ/WsduKtTzzq7SFbLjL7qTuWhtfBLONFQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4031
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BlZdGyydwBu2NioyE7fbasaEHd0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 07:02:51 -0000

Zhenqiang, Ron,

The PSP/USP/USD flavors are not -and have never been- related to SRH insertion.
One example for the PSP behavior is the first use-case that Wang described in his email. This same use-case is also captured in the companion illustrations document for NET-PGM Section 2.8.1. [1] together with a detailed packet flow.

Note also that the example that I provided in my previous email is for the USP flavor, which is one of the two that you are asking for. The decapsulation can only be achieved with the USD flavor which is different.

I believe that the technical aspects associated with PSP/USP have been addressed.

Cheers,
Pablo.

[1] https://tools.ietf.org/html/draft-filsfils-spring-srv6-net-pgm-illustration-01#section-2.8.1


From: li zhenqiang <li_zhenqiang@hotmail.com>
Date: Saturday, 28 September 2019 at 17:15
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>, "spring@ietf.org" <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Cc: draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt

Hello Pablo,

Without SRH insertion, PSP and USP are not needed. The example you give is decapsulation, not SRH pop.
I can not imagine the scenario that will use PSP or USP without SRH insertion. We need illustration to keep them in the draft.

Best Regards,
Zhenqiang Li
________________________________
li_zhenqiang@hotmail.com

From: Pablo Camarillo (pcamaril)<mailto:pcamaril@cisco.com>
Date: 2019-09-27 19:13
To: li zhenqiang<mailto:li_zhenqiang@hotmail.com>; spring@ietf.org<mailto:spring@ietf.org>; ipv6@ietf.org<mailto:ipv6@ietf.org>
CC: draft-ietf-spring-srv6-network-programming<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
Hi Zhenqiang,

Can you clarify what is the issue with the PSP and USP flavors and how it is related to SRH insertion?

For example USP flavor removes the SRH at the last segment (the final destination of the IP packet), before proceeding with the upper layer header processing.

Cheers,
Pablo.

From: li zhenqiang <li_zhenqiang@hotmail.com>
Date: Friday, 27 September 2019 at 10:41
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>, "spring@ietf.org" <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Cc: draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt

Hi Pablo and all,

Thank the authors for their efforts and quick reponse to the discussion in the list.
Since the SRH insertion parts are now removed from the base srv6 network programming draft, are the PSP and USP flavors appropriate to stay here? They do the SRH POP action.

Best Regards,
Zhenqiang Li
________________________________
li_zhenqiang@hotmail.com

From: Pablo Camarillo (pcamaril)<mailto:pcamaril@cisco.com>
Date: 2019-09-25 02:30
To: spring@ietf.org<mailto:spring@ietf.org>
CC: draft-ietf-spring-srv6-network-programming@ietf.org<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
Hi all,

We have just posted the split of SRv6 Network Programming.
The SR endpoint and transit behaviors that perform SRH insertion are now under a new individual draft (draft-filsfils-spring-srv6-net-pgm-insertion). This revision does not contain any other update.

As mentioned last week, throughout the rest of the week we will push another update with a few functional updates (e.g. NH=59).

Thank you,
Pablo (on behalf of the authors).


-----Original Message-----
From: spring <spring-bounces@ietf.org> on behalf of "internet-drafts@ietf.org" <internet-drafts@ietf.org>
Reply to: "spring@ietf.org" <spring@ietf.org>
Date: Tuesday, 24 September 2019 at 20:23
To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Cc: "spring@ietf.org" <spring@ietf.org>
Subject: [spring] I-D Action: draft-ietf-spring-srv6-network-programming-03.txt


    A New Internet-Draft is available from the on-line Internet-Drafts directories.
    This draft is a work item of the Source Packet Routing in Networking WG of the IETF.

            Title           : SRv6 Network Programming
            Authors         : Clarence Filsfils
                              Pablo Camarillo Garvia
                              John Leddy
                              Daniel Voyer
                              Satoru Matsushima
                              Zhenbin Li
    Filename        : draft-ietf-spring-srv6-network-programming-03.txt
    Pages           : 42
    Date            : 2019-09-24

    Abstract:
       This document describes the SRv6 network programming concept and its
       most basic functions.



    The IETF datatracker status page for this draft is:
    https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-network-programming/

    There are also htmlized versions available at:
    https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-03
    https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-network-programming-03

    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-srv6-network-programming-03


    Please note that it may take a couple of minutes from the time of submission
    until the htmlized version and diff are available at tools.ietf.org.

    Internet-Drafts are also available by anonymous FTP at:
    ftp://ftp.ietf.org/internet-drafts/

    _______________________________________________
    spring mailing list
    spring@ietf.org
    https://www.ietf.org/mailman/listinfo/spring


_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring