IETF Logo Mail Archive

Re: Network Programming - Penultimate Segment Popping

"Darren Dukes (ddukes)" <ddukes@cisco.com> Thu, 05 December 2019 16:50 UTC

Return-Path: <ddukes@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 C8E4412021D; Thu, 5 Dec 2019 08:50:08 -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=RJwtugxS; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=SAwTclfJ
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 J86doWgBDO9a; Thu, 5 Dec 2019 08:50:07 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D246012012D; Thu, 5 Dec 2019 08:50:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15261; q=dns/txt; s=iport; t=1575564606; x=1576774206; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3e/l5Klj8uUi7eBwpJVfT7RN0G4osZZyJQiQ0kbUMNE=; b=RJwtugxS5P0cq2AXUx8a+a380Ky5OSzeNmn64HbYYVtSaj/tYqCq5CPO eQnh6HZudyM4nTNogJpMewGXGSng5Nb1ZmCufwh84alJXu0VZB2ReiikP R95xrJksPjfZvCOEyZIh2fcWgSdiENBFOjxwBIweKg/+Kr/UGhWFBGm6P E=;
IronPort-PHdr: 9a23:yOYzfxLmcZM/PzRPpdmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeCtKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXEH3Mf3ndAQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CrAAAqNOld/5ldJa1lHQEBAQkBEQUFAYFrBwELAYEbL1AFbFggBAsqhCuDRgOKfJYBhGKBLhSBEANUCQEBAQwBARgBDAgCAQGEQAIXgXwkNQgOAgMNAQEEAQEBAgEFBG2FNwyFUwIBAwEBEBEdAQEsCwEPAgEIPwMCAgIlCxQRAQEEDgUigwABgXlNAy4BAgwDo1oCgTiIYHWBMoJ+AQEFgTUBgRSCPRiCFwMGgTYBhRuGexqBQT+BOCCCHi4+gmQBAQKBSUWCYzKCLI00gm2FT4lLjxMKgi6HH447G5omhD+STJFiAgQCBAUCDgEBBYFUAzSBWHAVOyoBgkFQERSMZoNzhRSFP3QBgSeQQAEB
X-IronPort-AV: E=Sophos;i="5.69,282,1571702400"; d="scan'208,217";a="671112142"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Dec 2019 16:50:05 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id xB5Go5pd012571 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 5 Dec 2019 16:50:05 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 5 Dec 2019 10:50:05 -0600
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; Thu, 5 Dec 2019 11:50:04 -0500
Received: from NAM10-DM6-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; Thu, 5 Dec 2019 10:50:04 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bk8VB0YAIU1LZkwOyl2xTaTeweOjKItxGBCe6Upt1TfShQvBKuLugL8xvrNkGEfuvJh92e/hLy66+ZkjjwR3yYbzRqtE2+piRUE+KS3AS1W6hKmBSZl7Prufwf0O0iBI4TahDgve1dAxZzEpOPdSL78TBiOYDH6dhl6A9f9lM6DNV3iCjZ03BPTyOaxG8jE9fqgwoZfLbSqFkEBJriC0B6ln58rK9Ceeu63aMx9E7lPHhgExRLMR19GZ68jQwWySJDduE/MG3laISf+R3+cW04gib8PxSLaDM7p924hr7vWQCv6nZIGNVSCXHh4ma5S36tYqMf7yxMHasE72u1rtsQ==
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=3e/l5Klj8uUi7eBwpJVfT7RN0G4osZZyJQiQ0kbUMNE=; b=S7yGwUiLR/BdpRyWZVrUFo0aeXAoT3rFaX8tefxqAY3/ZEEykMz8JLfM+Vk6dqliJvuUIlxhBCDPY03MTbXbYwv7XGy7deTnTSPvlqCKp0fSoFudLZVRUrkcZrIghiyZadTXEC4w63Nb95pvaIigdKi4JOAYDhubj8KcgRNxqWcI+M26kG5WL1aHQF6nFXN7fHBcWD0+4ZaRXyA/TQSbpxkGxV5mRqJadztmGA/GZYh9Ogq5FyqXKd+hXS4IH+q5s77Dq+glJZ0vHt5u9PpWMPkwINl6sXOqvaJ9jSm/9srnfxdCwsOSRBxZlK+8GRnXg2Oxjj9peNElLFtNBkHSWw==
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=3e/l5Klj8uUi7eBwpJVfT7RN0G4osZZyJQiQ0kbUMNE=; b=SAwTclfJaeAieXkYP8KftZOC/baV1ZJny7uHCl9GguV3rN9H2Vbx36iSdV26NhtfkwBZCDIletA68Ux3QtB3nObxIxu/gA79F1oTdfb5d+KUsFHsPL3Kj2/dWBh2WomBHSRSD1WqeI90ekpkBaB4raXCdj+blCiS6WDmDY7dxNI=
Received: from BN7PR11MB2594.namprd11.prod.outlook.com (52.135.246.159) by BN7PR11MB2739.namprd11.prod.outlook.com (52.135.252.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.14; Thu, 5 Dec 2019 16:50:03 +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; Thu, 5 Dec 2019 16:50:03 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
CC: SPRING WG <spring@ietf.org>, 6man <6man@ietf.org>
Subject: Re: Network Programming - Penultimate Segment Popping
Thread-Topic: Network Programming - Penultimate Segment Popping
Thread-Index: AdWqwAHVKZEn9oMNQKewBt9OvTlYXgAzAekA
Date: Thu, 05 Dec 2019 16:50:03 +0000
Message-ID: <3AD3BD11-8C34-41FE-B88F-49A9F2561D78@cisco.com>
References: <BN7PR05MB56998A05469327E759B5B671AE5D0@BN7PR05MB5699.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB56998A05469327E759B5B671AE5D0@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:1008::f1]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 16ec5ca7-cd61-4b29-0b66-08d779a32cbb
x-ms-traffictypediagnostic: BN7PR11MB2739:
x-microsoft-antispam-prvs: <BN7PR11MB273912B35B1A8FA87260EA8EC85C0@BN7PR11MB2739.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 02426D11FE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(136003)(366004)(39860400002)(396003)(189003)(199004)(316002)(6512007)(6486002)(2906002)(81156014)(81166006)(8676002)(54906003)(54896002)(4001150100001)(229853002)(5660300002)(478600001)(14454004)(8936002)(6506007)(4326008)(66476007)(25786009)(2616005)(86362001)(11346002)(53546011)(99286004)(186003)(91956017)(71200400001)(71190400001)(966005)(102836004)(76176011)(64756008)(66556008)(76116006)(36756003)(66446008)(66946007)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR11MB2739; 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: Pi2yWN1AzPmIa+QPhJ17613Yn1OEZZBh7LAXKYl/W3xJe4OrJ4MR/lglSVbNU1KF2M3fPYMFVpl/DRPX2+b8UgSRwAVGg10W1E+8dYMZ3oyfn8vlufhW01qwMRwtzVsnlFkbcrxxfjlQPD0UnbDeA1Uggg17kV4YERb74hKReb3h7cFPrG9bHHVuhY4lFNRsyLpz9yczhJTTieeY2JAynKSfTzVvzNHsHwbvdd5JnIPFZeoWKoXVEL+BjLCyABdP4OTGhUYo1x44GR+bnYsCV2OK471tW3YTDfDOcqpD3LsLQjyTRx3zjVhLa1c3MAO+IgoTwQf6/RH++aA6RdP0Rt9NlsIT3eqZv9a4XLqjod1e53vftOS4mLptqk7saozEgB1cOao4Ve8sAZSAgLAOB4beHvyAJbJUmeko6834RDLuMV64B+kmXTlht8YdXS8F46RJ+qGwXnvXvhZ4zb/10OrOTYuA/P5aqlB77MEKD1c=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_3AD3BD118C3441FEB88F49A9F2561D78ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 16ec5ca7-cd61-4b29-0b66-08d779a32cbb
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Dec 2019 16:50:03.1481 (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: WqfUbZrGlQEYWhsNnp1GJwhjUfHO2rpXDy2icRTDGgDl6aMRptyikCCAlhHy6wW2xgvbsf5zvqoJtqz/38S/Gw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2739
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.23, xch-aln-013.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/X5cE3Xo0IaMZg85d8qd3M9chiuA>
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: Thu, 05 Dec 2019 16:50:09 -0000

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
[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> 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
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email