Re: [spring] Network Programming - Penultimate Segment Popping

"Darren Dukes (ddukes)" <ddukes@cisco.com> Fri, 06 December 2019 21:14 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 9A60C12006B; Fri, 6 Dec 2019 13:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.399
X-Spam-Level:
X-Spam-Status: No, score=-14.399 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, HTTPS_HTTP_MISMATCH=0.1, 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=h41c/9M4; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=JJpJktb0
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 8nUzqFc8C-Hj; Fri, 6 Dec 2019 13:14:01 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D0F012002F; Fri, 6 Dec 2019 13:14:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26255; q=dns/txt; s=iport; t=1575666841; x=1576876441; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=TTCF4jQmqLoVK1i8QFenxRBRDJWjn8GZb+DiREhCbsE=; b=h41c/9M4zlptEdY6qr4JAtqiDnY/1MJEh6ftQ+umOTeQvixQamK6V150 WSUifUvBbTOWuFKcyQswe9LSaWfKYvc6K2O5wUXMo9D3LosrcKuN8iAn4 n7toXXsyxr5S4XUyVvOfxddnWO9SHYYnP6geUsll6wYueuxuHcI/Ey9+c 4=;
IronPort-PHdr: =?us-ascii?q?9a23=3AC4u/aB3RrPSialhEsmDT+zVfbzU7u7jyIg8e44?= =?us-ascii?q?YmjLQLaKm44pD+JxGOt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSw?= =?us-ascii?q?dDjMwXmwI6B8vQBUHmL/PxRyc7B89FElRi+iLzPA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DwAAA9w+pd/4wNJK1lHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgWwFAQELAYEbL1AFbA9JIAQLKgqEIoNGA4sBgjolmAWBLhSBEAN?= =?us-ascii?q?UCQEBAQwBARgBBQ8CAQGDCoE2AheBfiQ2Bw4CAw0BAQQBAQECAQUEbYU3DIV?= =?us-ascii?q?SAQEBAQMBARARHQEBLAsBDwIBCA4DBAEBKAMCAgIlCxQJCAEBBA4FIoMAAYF?= =?us-ascii?q?5TQMuAQIMA6FpAoE4iGF1gTKCfgEBBYE1AYEUgk4YghcDBoE2AYUbhnwagUE?= =?us-ascii?q?/gTgMFIIeLj6CZAEBAoFJICUJgloygiyNOYJuhVCJTo8WCoIuhyOOQhuCQod?= =?us-ascii?q?zhECLPIQ/kk+RZgIEAgQFAg4BAQWBWQcrgVhwFTsqAYJBUBEUjEIkg3OFFIU?= =?us-ascii?q?/dAGBJ4xAAYEPAQE?=
X-IronPort-AV: E=Sophos;i="5.69,286,1571702400"; d="scan'208,217";a="388673617"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Dec 2019 21:14:00 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id xB6LE0JB000382 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 6 Dec 2019 21:14:00 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 6 Dec 2019 15:13:59 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 6 Dec 2019 15:13:58 -0600
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 6 Dec 2019 16:13:58 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DDf4jcz47LyM+HCDrYZc7FXLBnIVZlHhBwij8XwEb/dlX5WaMTVKXmY6MWleJQNvitXOejSp/gJrvVI3xzKJwONekx3HijBHiHiZSvr1nWL/F0JCBjZSCVIhk7AjuRRWKfErQZ7tXiIll6NZoNYg/c1/223h1R8Riij9xDKhUqx+oIH59VaIXVYDmpbbO+VwOr0CuD/HjA95kXpxZmhysVtl3OwaHXut96ZC7L93k677QLf4BOxkzFVGX/yy8NQTpyNbuLB/129DVJfNyoXCJT8/IwLbZBzB0ind73uCC9Uk+AEsXS3dt22HrjOdfFAMJS9eF6ttOkvBzjXXFPeQkQ==
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=TTCF4jQmqLoVK1i8QFenxRBRDJWjn8GZb+DiREhCbsE=; b=Y2yV8GaYxtL+LSCp2hkH8fHoN0sESOEDcOARc/TweiAxIvlS+MN0ZiwRdHxPFzLbrAk8l6tC5LeRNizW2oP8o093CN+iJ3IdWDYB1QaeYEdnVE6PA7leSEFTXYGGOuE9vbsntL0T/UPL4euDDrYj+/GzRDLQL4FfLG/MjUwn1202TO533o9H5yVR6mHtL32wWsjC11P99PBxQ/iSx/8hkA70hCmlIIjskZ/gEQe2Nj8NLzs5scfBMaL5u2yIVpVlAzfLXpZi+twxwf98sVwbm2kN2H9ZaVYv4rad49YhtHw5ed+s3TuQ4Vy0blgrS6TT2g3FvCV8FJSdFWUAHXPCjw==
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=TTCF4jQmqLoVK1i8QFenxRBRDJWjn8GZb+DiREhCbsE=; b=JJpJktb0GH/OIi4XZ/Kuh/rbMdKtYtqnfwmf9I2R65VXMPxgbiE2cp+u3vUhD0zw9+QNMAYmucKefdA3OnQXS6D2+ONvBap3C/mtSRpVH70Ywjk67GWfitFyt3HMTnM3g1ycdNrhrT/kLDd/2fXC/p3xqJEfIxnhtODPZ/KH53o=
Received: from BN7PR11MB2594.namprd11.prod.outlook.com (52.135.246.159) by BN7SPR01MB0016.namprd11.prod.outlook.com (20.176.178.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.12; Fri, 6 Dec 2019 21:13:56 +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; Fri, 6 Dec 2019 21:13:56 +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: AdWqwAHVKZEn9oMNQKewBt9OvTlYXgAzAekAAAP9pMAAN4RDgA==
Date: Fri, 6 Dec 2019 21:13:56 +0000
Message-ID: <D6B1AED6-0AB2-4394-9503-7A1885BC8B40@cisco.com>
References: <BN7PR05MB56998A05469327E759B5B671AE5D0@BN7PR05MB5699.namprd05.prod.outlook.com> <3AD3BD11-8C34-41FE-B88F-49A9F2561D78@cisco.com> <BN7PR05MB569946D6AA5C6B78AFC05F6BAE5C0@BN7PR05MB5699.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB569946D6AA5C6B78AFC05F6BAE5C0@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: [161.44.213.3]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 24cb7762-227c-4ce8-94ea-08d77a913457
x-ms-traffictypediagnostic: BN7SPR01MB0016:
x-microsoft-antispam-prvs: <BN7SPR01MB00164587E12EB379EF2EF843C85F0@BN7SPR01MB0016.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0243E5FD68
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(396003)(366004)(346002)(136003)(189003)(199004)(26005)(91956017)(5660300002)(76116006)(71190400001)(76176011)(71200400001)(186003)(966005)(316002)(102836004)(2616005)(4001150100001)(2906002)(66946007)(66476007)(66556008)(54906003)(66446008)(6916009)(64756008)(86362001)(53546011)(8676002)(8936002)(36756003)(229853002)(6506007)(6486002)(33656002)(6512007)(478600001)(4326008)(54896002)(99286004)(81156014)(81166006)(19607625011); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7SPR01MB0016; 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: wKVF0OLgS9gKELfU7SndW8DUdE9Ba2+mrxSzZv1/38KkArJE9qL3BibJ2q4TigTRbIyEFmetMW414inisJyPER/VFqgc9Ega+9UoSgearilDIkHTdFnjknEOIQ1gOYN2aZM8FDJSOkGRwHSz70obZvqJPA8+k7TCjFkn3dWZjGXajteDEyIUKPSGmls/uk13sof/DCslmMKRvi/DEMzEJ5gY40AMnz5qtAxOooLTjJCzvMtJoeQFQ6xYllxTBJNjn58vv+xkBoJqbynSeqCwtILWNlYkkNSv/tKp+ebAM+8lXLc5kDxc38/Jw6uobEBwA2PlFB25UvDSWYinnlb5KMkc3DrCisIoaGUI80Q18G+safOH0Vnzaso5x4Gc8hcAmhoPWd7kB64fRX2v726R6RTcn0px7vpT5nB1aEU3ONdJAXsDBBQV9dnROuBfUQlH3h9O8WUK48JKcSPNM9D22wvz2NFlDyuFrNI+hmnbAiOjScXRI5APeSITWg7BHUuVc0ZhzbcE5QAr6rqLtnkADwYpwxkusHeThjPNrdhp4oY=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_D6B1AED60AB2439495037A1885BC8B40ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 24cb7762-227c-4ce8-94ea-08d77a913457
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Dec 2019 21:13:56.0727 (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: dIJwd/4QCNIwHNlQly7rn1k3KHK3bEkindhYLWUc96DruDy+KkM+sx1z2Mn8bEdomo/TMapWmIjE75ODeJs08A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7SPR01MB0016
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/M3_KWkvu-wVYYODdPKGhkNctg2Y>
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: Fri, 06 Dec 2019 21:14:04 -0000

Hi Ron. I am trying to be precise in my posts.  Please do not interpret them as dismissive.
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.

I have used very specific words to describe the PSP operation within an SR Domain since they are easy to find in RFC8200’s discussion on the topic.

“The SRH is only removed by the node identified in the destination address field of the IPv6 header.”

The PSP behavior does belong in network programming.

Thanks
  Darren

________________________________
From: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Sent: Thursday, December 5, 2019 3:39 PM
To: Darren Dukes (ddukes)
Cc: SPRING WG; 6man
Subject: RE: Network Programming - Penultimate Segment Popping

Darren,

I understand that the PSP operation:

  *   Is executed on the penultimate segment endpoint only
  *   Is signaled by the source node using bits in the IPv6 destination address
However, those facts are orthogonal to the question that I asked. So, I will try to ask my question again. Please read it carefully and answer the question that is asked. (Dismissive responses will only make me grumpier.)

Currently, there is no consensus that IPv6 allows insertion of extension headers by intermediate nodes, even if those intermediate nodes are segment endpoints . Given this lack of consensus, the authors of network programming have wisely agreed to remove header insertion from the draft.

Likewise, there is no consensus that IPv6 allows removal of extension headers by intermediate nodes, even if those intermediate nodes are segment endpoints. Why, then, have the authors of network programming not agreed to remove PSP from the draft?

                                                                                           Ron




Juniper Business Use Only
From: Darren Dukes (ddukes) <ddukes@cisco.com<mailto:ddukes@cisco.com>>
Sent: Thursday, December 5, 2019 11:50 AM
To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Cc: SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>; 6man <6man@ietf.org<mailto:6man@ietf.org>>
Subject: Re: Network Programming - Penultimate Segment Popping

Hello Ron, I believe this is the fifth time you have raised this comment in 6man and/or spring.
The comment has been addressed in earlier iterations.

Let me recap.

With the PSP behavior, the SRH is only removed by the node identified in the destination address field of the IPv6 header.

That destination address was placed in the SRH by the SR Source node, fully expecting the behavior.

Thanks
  Darren

Iterations:
[2019-09-06] https://mailarchive.ietf.org/arch/msg/spring/7zMgIwEY9AipZCCGO9KnT2CGH3o<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/spring/7zMgIwEY9AipZCCGO9KnT2CGH3o__;!8WoA6RjC81c!T981Kv39IIsXJ2I3jiE36cVdwwLgIWJoFBUg_AnU8IEb9Y_6GbNWAykRc82ck-xk$>
[2019-09-27] https://mailarchive.ietf.org/arch/msg/spring/4_Slu3kkHwduZZPFJJmRUkmoTVo
[2019-10-14] https://mailarchive.ietf.org/arch/msg/spring/u536YH4tv7kKRq_b9_x9gBYpO9c
[2019-10-21] https://mailarchive.ietf.org/arch/msg/spring/4pikRli_HSECun9AbwfpmOF5KLI
[2019-12-04] https://mailarchive.ietf.org/arch/msg/spring/oDWLbRDqKCaF5Xa-QvKY6mk_D5E


On Dec 4, 2019, at 11:37 AM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>> wrote:

Pablo,

It seems to me that the following are equally controversial:


  *   A transit node inserting a Routing header
  *   A transit node removing a Routing header


We have agreed to move discussion of RH insertion out of the Network Programming draft and into another draft. Shouldn’t discussion of RH removal be treated similarly.

This comment applies to Penultimate Segment Popping (PHP) in the Network Programming draft.

                                                                 Ron


Juniper Business Use Only
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/ipv6__;!8WoA6RjC81c!T981Kv39IIsXJ2I3jiE36cVdwwLgIWJoFBUg_AnU8IEb9Y_6GbNWAykRc6EiWnkb$>
--------------------------------------------------------------------