Re: [spring] Network Programming - Penultimate Segment Popping

"Darren Dukes (ddukes)" <ddukes@cisco.com> Sat, 07 December 2019 15:10 UTC

Return-Path: <ddukes@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 A4DA212008F; Sat, 7 Dec 2019 07:10:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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=S8t8Cfny; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=WUMMz43E
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 1ILL3kIz7E17; Sat, 7 Dec 2019 07:10:10 -0800 (PST)
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 06A7E12001E; Sat, 7 Dec 2019 07:10:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11149; q=dns/txt; s=iport; t=1575731410; x=1576941010; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SVrdjo13hagGZy41+PPiO8sRCdM7WndiGAxeEpRne2Y=; b=S8t8Cfny3VYiFeBLx96OCfIf1U41dfIWVL21I7cUK8VxUmwIWuXOdlqm AMccxl92PoQcanRdMvKAQN5Mqpml6Tjq06KLUKzJ9p0Fy8nDsa4H3cWhO /brszMO/E/mYjXRFFho2VyhrTCbIgfUh8MqbJey5MzPECUwtQ7pRCeu2r c=;
IronPort-PHdr: =?us-ascii?q?9a23=3AYEsVphyaTSwOxlzXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuJBVD4IeXCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DtCgB4wOtd/4oNJK1lHgELHIMaL1A?= =?us-ascii?q?FgUQgBAsqhCyDRgOLAII6JZMjhGKCUgNUCQEBAQwBAS0CAQGEQAIXgX4kOBM?= =?us-ascii?q?CAw0BAQQBAQECAQUEbYU3DIVTAQEBAgESER0BATcBDwIBCA4xAwICAjAUEQE?= =?us-ascii?q?BBA4FIoMAgXpNAw4gAQKgSwKBOIhhdYEygn4BAQWCSoJNGIIXCYE2jBgagUE?= =?us-ascii?q?/gTgMFIIeLj6EEoNHMoIskCeFUJhmCoIulWYbmjKEP6Q2AgQCBAUCDgEBBYF?= =?us-ascii?q?pIoFYcBVlAYJBUBEUjGaDc4pTdIEojgWBYl8BAQ?=
X-IronPort-AV: E=Sophos;i="5.69,288,1571702400"; d="scan'208,217";a="675464586"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Dec 2019 15:10:06 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id xB7FA3TD001927 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 7 Dec 2019 15:10:05 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 7 Dec 2019 09:10:02 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 7 Dec 2019 09:10:02 -0600
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 7 Dec 2019 09:10:02 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hew0SgIGzFtDeECJ5jSH2WE/OzjUxPvlrE3DIZtqrLOSxD4TcDSGd1eQ+601OQOd1RGnDmWJtzv5r0lsy6xTsT9nrD4cA+5bKJCBMXJ8A/ItZ7ppDOwZLZBs0h+1Zg9Atxsy0ue9MbeFsq6FXHupjlRmyq0gG2kzmnmV/MWyRtN72gwITNdbYY/T7Sq9SEiP/9h4HGdfYCMNAhnD9g2+bz/v3tF6TcQtb5fNOrNte+wszwGGUFOf5bjRbbIJM2VlWRcPCUjEHcEFwRt97h8QvrSyp05TxmVtC5yRhn03Rp2WI9ddmwUklvOzUIhtkW4t7gc87ko61UJvZ+pW3RQDTQ==
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=SVrdjo13hagGZy41+PPiO8sRCdM7WndiGAxeEpRne2Y=; b=fxSlCIxVi4+5zlZ3rslJ4j1C4HSXKWMokSvU3aMv/7k24vp+zhXzWuTEhoFMB8hRHjeOtg83o4fqHJmVVZRqoEI8BpBWoPbrW2MUFjL868lIeBC+BxGJnKkQUz3HokUAT+vNA+KVH/VTa0Ei4O2aqsxzzCGqbeYnc92yFowTUHY1qPJQdP9BekwTRZueZQxi/jWSaBTvmuRRzlp9Z5dSjCfX5PLUHGtJKLSoQLaeGGmyxFZ9sxb1g7TudR4USlxeQRnePA46CIlUQqUzC16Oovp6a1r1ktduV2wOvouAeiL8eo+od2+Ri+B676LwO6GbZiPqpqJ7qemYv0SF1WYhRA==
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=SVrdjo13hagGZy41+PPiO8sRCdM7WndiGAxeEpRne2Y=; b=WUMMz43EItqweIJzoA+m3jQcXwEz2v8G9dYKnS0KqI4aPJSbfy05Rgs8dVrAB3hKQQsm8bm7V9pY7VnvszEdfgbzE8qht1tuY9ZsLbj5RVMqFZpeqi55SjE5ThJ9xA308HuJRImvmHFiZhXMhwk4WgulayopFdfhjyY4dST7ILI=
Received: from BN7PR11MB2594.namprd11.prod.outlook.com (52.135.246.159) by BN7PR11MB2835.namprd11.prod.outlook.com (52.135.254.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.16; Sat, 7 Dec 2019 15:10:01 +0000
Received: from BN7PR11MB2594.namprd11.prod.outlook.com ([fe80::c72:fa12:757e:cca3]) by BN7PR11MB2594.namprd11.prod.outlook.com ([fe80::c72:fa12:757e:cca3%5]) with mapi id 15.20.2516.014; Sat, 7 Dec 2019 15:10:01 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Ron Bonica <rbonica@juniper.net>
CC: SPRING WG <spring@ietf.org>, 6man <6man@ietf.org>
Thread-Topic: Network Programming - Penultimate Segment Popping
Thread-Index: AdWqwAHVKZEn9oMNQKewBt9OvTlYXgAzAekAAAP9pMAAN4RDgAABYu/AACQyAAA=
Date: Sat, 7 Dec 2019 15:10:01 +0000
Message-ID: <7B7CFEB8-80F0-4690-9BE3-8D5F935E148A@cisco.com>
References: <BN7PR05MB56998A05469327E759B5B671AE5D0@BN7PR05MB5699.namprd05.prod.outlook.com> <3AD3BD11-8C34-41FE-B88F-49A9F2561D78@cisco.com> <BN7PR05MB569946D6AA5C6B78AFC05F6BAE5C0@BN7PR05MB5699.namprd05.prod.outlook.com> <D6B1AED6-0AB2-4394-9503-7A1885BC8B40@cisco.com> <BN7PR05MB5699C73EF0EE1F8E7A96C738AE5F0@BN7PR05MB5699.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB5699C73EF0EE1F8E7A96C738AE5F0@BN7PR05MB5699.namprd05.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=ddukes@cisco.com;
x-originating-ip: [2001:420:c0cc:1006::30]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3d27235f-1afe-45b2-3a5f-08d77b278827
x-ms-traffictypediagnostic: BN7PR11MB2835:
x-microsoft-antispam-prvs: <BN7PR11MB28353EC3B03CCC42CC6313D6C85E0@BN7PR11MB2835.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0244637DEA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(136003)(39860400002)(346002)(396003)(376002)(189003)(199004)(66446008)(76116006)(66476007)(91956017)(66556008)(2616005)(102836004)(229853002)(54896002)(5660300002)(478600001)(6512007)(64756008)(53546011)(4326008)(6506007)(99286004)(316002)(33656002)(186003)(76176011)(6486002)(36756003)(54906003)(2906002)(66946007)(71190400001)(71200400001)(86362001)(6916009)(8676002)(81166006)(81156014)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR11MB2835; H:BN7PR11MB2594.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: m1HjMr91silm4oXJVVmDXSPCvQHceUi2y90o3YsJtoTODkeTsjX8l/PJp1i1o70xU/an42WHmFXN9eLZ9I85fwfzY8pN6G6HJOjnvlEbM5I07KdabZkkkGtayCHMrFu9rjDiXdEtJdqAAYt/RreyetZ7UJgqoGtnlgLBoU6159Ti5OvCbWcnkLk2CD5SXgu7sP04/FtGPw90haEgjAibAi7DaZSkh0NzcGOIYqDz+C3SDCKhwlSsmAgiPE+81SobtkD5XgF6iBQFFk1boWUJe+2eJILYSHLtva4i4Q8W3niy/V9mz5k4E+FUKoPto52+E+DYkD+dD5P6nndndRq5wmJMJiITJ8MSEaPIPKK9lwtYMc9lPs/Zgi02V4T1icZ2y1Kgwc7byPExiyq1E/U7o3skhDX08p7qRxkI7cqQJm7jPN0O9FmCLFWH6EmdLzrg
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_7B7CFEB880F046909BE38D5F935E148Aciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3d27235f-1afe-45b2-3a5f-08d77b278827
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Dec 2019 15:10:01.3258 (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: Ml+R707Z42oyACQDyd4lP6q7KM2wmRCObOkx00y0/Ww7QSNJBgBc+Tby9hapGoSg5t++6XCV6jxhtMdhAderMA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2835
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.18, xch-aln-008.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/JdpSLS7ax0VUZLG6SINxnOWJzbY>
Subject: Re: [spring] Network Programming - Penultimate Segment Popping
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: Sat, 07 Dec 2019 15:10:12 -0000

Ron, you say
>>  RFC 8200 addresses extension header insertion and deletion identically, in the same sentence.

This sentence you refer to clearly permits PSP as defined in network programming:
   Extension headers (except for the Hop-by-Hop Options header) are not
   processed, inserted, or deleted by any node along a packet's delivery
   path, until the packet reaches the node (or each of the set of nodes,
   in the case of multicast) identified in the Destination Address field
   of the IPv6 header.

Clearly we process the SRH at the node identified in the destination address field of the IPv6 header.
With PSP we remove the SRH at the node identified in the destination address field of the IPv6 header.

I think it’s clear we can conclude this thread.

Darren



On Dec 6, 2019, at 5:01 PM, Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>> wrote:

>> I have observed, in your original post, the conflation of SRH insertion within an SR Domain with the PSP behavior defined in network programming.
>> Whether this was intentional or not, I do not know.
>> Regardless, it is wrong.

Darren,

We clearly disagree.  RFC 8200 addresses extension header insertion and deletion identically, in the same sentence.

                                                       Ron






Juniper Business Use Only