Re: [spring] Network Programming - Penultimate Segment Popping

Ron Bonica <rbonica@juniper.net> Thu, 05 December 2019 20:39 UTC

Return-Path: <rbonica@juniper.net>
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 CA35C1200E6; Thu, 5 Dec 2019 12:39:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=WSnt5suh; dkim=pass (1024-bit key) header.d=juniper.net header.b=EajZi9sa
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 wXs90_mG4aXi; Thu, 5 Dec 2019 12:39:21 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1F201200CC; Thu, 5 Dec 2019 12:39:21 -0800 (PST)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xB5Kcp03018397; Thu, 5 Dec 2019 12:39:20 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=ebiqk1aSBFeuz67LqUFgLb6UPTdzIkA1vOgAnwmhKTw=; b=WSnt5suh+YL34+0kta1+Ddx1TIuv6XfAy3jbRQcz2NEDOM+5RGraB+843yTrm5Q5dLU+ KSoLR6sB1k5Tuai2W6uPfElxler/TT2UkZ0ncMker0AR6pBJldTVyBlEXk6/mCucKOpA 1w0uZ4wo8OJICwb/XjAuyJxw97xyY3HJVNDfjDi6jqAjAaasUXdSIZCya8aOCAFtelhQ 2NaGNySBVktC/To6bY03mox5js/14ymTNhW003RCvEx2kPqPwa/W7p3j64KPc1qbVDSj HTyqEZZYw/4ZhZyjVl+sJqWAPhOosE9oyyRgWE4Eo4gC3ewdrk8lYO4YVXDuG/t+RWTv WQ==
Received: from nam12-bn8-obe.outbound.protection.outlook.com (mail-bn8nam12lp2175.outbound.protection.outlook.com [104.47.55.175]) by mx0a-00273201.pphosted.com with ESMTP id 2wp2ae3yuq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 05 Dec 2019 12:39:20 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IL4bxWBmzkmKEHlisbd3GOkKfH9Rnlkl8lCxgZFSsh666MBwwyyXM1S26tkZy3VRoa0yziXnEyEE4pSsHyqyHTVprzXvxod15kulMVXX0BVvMTN6jSFhtV36EQVrCdWjl/rYTNA2sZ7IBw9hrQd8uevVaOVnxpC9tZdZIKVOddb5YLY8hFT/kLoD2mes6b7BjexDwMYWpe2teg3dt/6EUXde2MNn+eHEfnuz/g+mJeq6uWvasVPHqF1Nl/gYaSPVd1QodBgBRZwUu8TTRUBzfDYbwwXrhUBd+bG8kdvbygCwthS2YYsj11+BJcOCZ267GoS0AJjXYeDo3g/SNoDwUg==
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=ebiqk1aSBFeuz67LqUFgLb6UPTdzIkA1vOgAnwmhKTw=; b=kcRypZoQ298iijX9TSbilUzyfD/gv7F1l69n/srb5efMHIWo4KvpGhfjphOJP6wZX8edyCxLhN7uh7jRCcwbla/Z82XmDUGgxZ9i4esQJK2ESKuTp8ULFfuD1PDcbz7LZp407wuKQZZd2nn4whePR99v6NgFVRV2D2bDgQhJSFqTiGEIPGr+jIqlOKISb5Djy9rPz9dtFLXjzO7p/GOBaE5fmJ7qYtcd+o0frBpX/+dr30HZQ+mOFONBvOuMy/vlN3ujQc7GYlA50N1d4jjXvugrG4i2vsqR/mYz91l2Wh6l2lAmhKK1pTb0lfNXUUnRh8CVAbcg26IEWCFVcc50bA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ebiqk1aSBFeuz67LqUFgLb6UPTdzIkA1vOgAnwmhKTw=; b=EajZi9sayAsYw+fvkehUGkaXxIOjK4M2NAQ3cenabwaYSii+fj5EnaygTCkqyGQ3DD1EjqYDYGFQ+2iFPbFGMmVNbO/a6OB9j95TDx6zYNFpNtOjqTBvDVM/eNFgw5ftY3ah9dLT++3RQjRoP8pC6MM6Oizt4IvI+ixrApB15Wk=
Received: from BN7PR05MB5699.namprd05.prod.outlook.com (20.176.28.88) by BN7PR05MB4212.namprd05.prod.outlook.com (52.132.220.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.8; Thu, 5 Dec 2019 20:39:17 +0000
Received: from BN7PR05MB5699.namprd05.prod.outlook.com ([fe80::185e:d297:6499:4987]) by BN7PR05MB5699.namprd05.prod.outlook.com ([fe80::185e:d297:6499:4987%7]) with mapi id 15.20.2516.003; Thu, 5 Dec 2019 20:39:16 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "Darren Dukes (ddukes)" <ddukes@cisco.com>
CC: SPRING WG <spring@ietf.org>, 6man <6man@ietf.org>
Thread-Topic: Network Programming - Penultimate Segment Popping
Thread-Index: AdWqwAHVKZEn9oMNQKewBt9OvTlYXgAzAekAAAP9pMA=
Content-Class:
Date: Thu, 5 Dec 2019 20:39:16 +0000
Message-ID: <BN7PR05MB569946D6AA5C6B78AFC05F6BAE5C0@BN7PR05MB5699.namprd05.prod.outlook.com>
References: <BN7PR05MB56998A05469327E759B5B671AE5D0@BN7PR05MB5699.namprd05.prod.outlook.com> <3AD3BD11-8C34-41FE-B88F-49A9F2561D78@cisco.com>
In-Reply-To: <3AD3BD11-8C34-41FE-B88F-49A9F2561D78@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=rbonica@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-12-05T20:39:14.9816881Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=1e530d70-76cb-4039-8314-d2d84ab25dd1; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
dlp-product: dlpe-windows
dlp-version: 11.3.2.8
dlp-reaction: no-action
x-originating-ip: [108.28.233.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 6be4a8ae-a4af-4425-d3d6-08d779c33271
x-ms-traffictypediagnostic: BN7PR05MB4212:
x-microsoft-antispam-prvs: <BN7PR05MB4212658B5BF59F4BD3FF948BAE5C0@BN7PR05MB4212.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 02426D11FE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(346002)(396003)(376002)(366004)(189003)(199004)(54906003)(66946007)(4001150100001)(478600001)(33656002)(966005)(76116006)(8936002)(64756008)(26005)(52536014)(53546011)(11346002)(7696005)(76176011)(74316002)(66476007)(186003)(66446008)(2906002)(66556008)(4326008)(102836004)(6506007)(71200400001)(6916009)(8676002)(55016002)(5660300002)(71190400001)(25786009)(81166006)(99286004)(229853002)(81156014)(86362001)(9686003)(14454004)(316002)(790700001)(54896002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN7PR05MB4212; H:BN7PR05MB5699.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: uB9+l6v565++X3kzQX/sJCgAbam6WeVHgFgSPemu7pvfl774IiCMIE7Jv3hZacc3SBA53LVCM0ojG7gSIwWbjVkYmBFCOGwUjWGnm7ZrQL14n/Eawuy4Zlno5v+PDgKIniRRzLyGUGhXpgzPLtCKWa7/1TQszvbYyTiZHO6ueTZW26gj56C7+uhGavbKUM87bmCmE3bYqykVfShEe4wmJfGR8DrTbV9Z/+xqO+9bp7l05Ip+CGaQrXvZXhFv2An7uLPOuyAze0jR+kfNSAlg4Cpif3nx5Sz04SpmpRu+ecLhh9e90LYqcQCK3qfm1BB2HtYoTBNKSKkA0XjY0tBIoI7wxt4PvhwJQJiDioykPiNQC+WPKeQsSEOJOWTrDt37Ov01OiE0i8co1KdyqWCC26+snoqW77rKIrH9EjdTUGEodsB8w02Naf0ZJCGOZmpPQ7LpOEZQcJ/OLPf77VJpUXXtx893pAry78URblqGzZM=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN7PR05MB569946D6AA5C6B78AFC05F6BAE5C0BN7PR05MB5699namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 6be4a8ae-a4af-4425-d3d6-08d779c33271
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Dec 2019 20:39:16.6839 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: m+po31uOkRbAeMinIPzKoLJBdSBEo0GIMD5YiBSdZlYtzYarfshFYH48Mpt8LgDM4nq2thoc6ASJIvvQuJzMcw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR05MB4212
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-05_08:2019-12-04,2019-12-05 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 lowpriorityscore=0 impostorscore=0 bulkscore=0 malwarescore=0 phishscore=0 mlxscore=0 suspectscore=0 spamscore=0 clxscore=1015 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912050169
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/h60MSdvoZiiLJV-EB57QEWUVtRE>
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: Thu, 05 Dec 2019 20:39:25 -0000

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>
Sent: Thursday, December 5, 2019 11:50 AM
To: Ron Bonica <rbonica@juniper.net>
Cc: SPRING WG <spring@ietf.org>rg>; 6man <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$>
--------------------------------------------------------------------