RE: What is necessity for SRH, and other EH, insertion/removal?

Ron Bonica <rbonica@juniper.net> Mon, 09 December 2019 02:26 UTC

Return-Path: <rbonica@juniper.net>
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 DD9C61200CD for <ipv6@ietfa.amsl.com>; Sun, 8 Dec 2019 18:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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, 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=lD47+JKa; dkim=pass (1024-bit key) header.d=juniper.net header.b=GBELeig9
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 knK4NtKjACnB for <ipv6@ietfa.amsl.com>; Sun, 8 Dec 2019 18:26:50 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 5B22112004A for <ipv6@ietf.org>; Sun, 8 Dec 2019 18:26:50 -0800 (PST)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xB92MeNQ025383; Sun, 8 Dec 2019 18:26:47 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=0ahvs4eCsvFCgZ4IYHpVJSoHGVK/COkRfY1LTKZKdfA=; b=lD47+JKa+1iRGTkCLs2TEOtd5blcuifBR57c3lZdOdLiWJSfiskF3qrx3BVn7YZcZn8s lLJaHCYkjwCOh24X6OZLSkVC95lakeD1B1nweySy0QkPFQt2aUrPUZdk+3BO83ZCwBo/ e4mexLlYhsVcAch1KctDj3YPn6En4mdhjTU5MiQ5iJc5gMp4SjRX6nraa0wQMVxkUPBk VkmQhIe7rmmhdXA+MMCLxhybILbapO5eTdrPW1ivepueoQ9k92+Rg8Gqjz86ThxV2tih qi1SB/atYHsNn0NoFNQbrhxydyfOT9VnYIqOukIBK3s7j/PteK1By3DkJxIq0Ou73i7U 6g==
Received: from nam11-co1-obe.outbound.protection.outlook.com (mail-co1nam11lp2174.outbound.protection.outlook.com [104.47.56.174]) by mx0b-00273201.pphosted.com with ESMTP id 2wravhsvbu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 08 Dec 2019 18:26:47 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dkowAql3VvFvMu7BKuHGwvKRkISZcbNtpIY21L/ECdItqmtL2cIqOoqup/ZEIAiGuA44gJQKx2UnnVpFO31lSooBCM5UadLpWbmkbUasurhz3k1woafBzFabZ7cfOSXJoaSSFeA/VpjTuD8tZxJxLaevGYbfWaLDk4VVUzlnBxND6JOLGd18VNJxFMGzi2yJzy61maaxtKr1Tfdi7OmCU5fNXJz/zFREsVIiMgT4B8l9TkZvmThXay7ZV7zx5AflN6zOIVw1DVd+ZtQzavK9A7wYd8LUS3AX34r3eTCHin9wOjL02sS+dhLtXSDwQG/l+mp2SZRb92T075qCDGUh9Q==
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=0ahvs4eCsvFCgZ4IYHpVJSoHGVK/COkRfY1LTKZKdfA=; b=YlCxg+ASVbvkRGOXYKhFXuIKq9nVJMaE3D+eF+HotRSZgE04Sk+jcrmhBw8U68ONyFHoyFzVSyMw+gq7n797z2mq0bXi9Dn4ORrZSBkUxcC99OeZEXzPDAJY95rIFHAFLdp6v0+XTdXB2Wj1fTJCgqyI8ZqkHof3gkb5ubJoqTr5y+Rj4NLPLeCSBHEcXI8vahizF4Syn2MQQelx4otTs0iR+W9mqFEkiW+oDrrXPfJUFI+XjW9BRMThLumq4IxmOPikCIuuIGJiLEC/hg5A2tvj+yjEKPuXB56UhMOcW2E8Y89RJySpqZdKjtMZE3VVzZpb9ykrp0HYo17XoQuvQg==
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=0ahvs4eCsvFCgZ4IYHpVJSoHGVK/COkRfY1LTKZKdfA=; b=GBELeig9tSqhOwHi/+2OToprVTDWpuI+ChQOae4cKkhv0reX2ZnOMdAbbpfnjdrgGNZjrKW0bwkRqmMF9/si0C+dbF/qs1NlMP0hnJ2FxaDYP1fLZLIrDvdMxNX6cUfwoiVA64TMgmlOlk33n+v4qyhoHeolaSBel00YGfms+mc=
Received: from BN7PR05MB5699.namprd05.prod.outlook.com (20.176.28.88) by BN7PR05MB4084.namprd05.prod.outlook.com (52.132.219.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.13; Mon, 9 Dec 2019 02:26:42 +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; Mon, 9 Dec 2019 02:26:42 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Tom Herbert' <tom@herbertland.com>, '6man' <ipv6@ietf.org>
Subject: RE: What is necessity for SRH, and other EH, insertion/removal?
Thread-Topic: What is necessity for SRH, and other EH, insertion/removal?
Thread-Index: AQHVrSI6ditkyykD50mwIA9TzeGMIaeu8ZoAgAIh1MA=
Content-Class:
Date: Mon, 09 Dec 2019 02:26:42 +0000
Message-ID: <BN7PR05MB56998243A0F4C8EE03D0816BAE580@BN7PR05MB5699.namprd05.prod.outlook.com>
References: <CALx6S34vG=L_5nw_FzxHBUy+7tbWH4dhOh8xodOfKf2oOdrarg@mail.gmail.com> <04a501d5ad25$f0745a50$d15d0ef0$@olddog.co.uk>
In-Reply-To: <04a501d5ad25$f0745a50$d15d0ef0$@olddog.co.uk>
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-09T02:26:41.3762772Z; 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=b5cc06d3-44b9-4eae-86ff-dce0a365a3ae; 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: 3653ef78-0d0b-403b-e62f-08d77c4f3ae6
x-ms-traffictypediagnostic: BN7PR05MB4084:
x-microsoft-antispam-prvs: <BN7PR05MB408455C69B6BBA6C218DC194AE580@BN7PR05MB4084.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02462830BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(396003)(346002)(136003)(366004)(376002)(13464003)(189003)(199004)(53546011)(6506007)(55016002)(33656002)(9686003)(71200400001)(71190400001)(478600001)(8936002)(8676002)(81166006)(81156014)(966005)(99286004)(102836004)(52536014)(186003)(74316002)(7696005)(229853002)(26005)(5660300002)(305945005)(86362001)(110136005)(2906002)(316002)(76116006)(66946007)(76176011)(66556008)(66476007)(64756008)(66446008); DIR:OUT; SFP:1102; SCL:1; SRVR:BN7PR05MB4084; 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: A6XJMBIKjjkINH3TvyKos19yIbggCPPwck3+c3N+T8m+CYn0y58ADasNk/8q5FEkfh68XQebz6WrQMIRInLErFDjyd1IKDjLG0wSKyazlfBMncoRogKil6SUZPgOLe/CxjBLFPWBnY1E21HB9drUm7Q0b8A168k0YQ29ike7x/fX73vTN6rXMFm8EGRvdYxsxDY4RgIFZCcacpiTsBaynWP+DpUw68tPwjGD0NiRZVVyODOkcAfYlyvMXV06j8D0SZ10vGAeh5Q40GoYO78/C62eopa4s43+8UXoOEQ6J9lMCMOmys5TMhLtbTQL8X2ixxwKYQZhY+5Sco3mWRSLAfhBlI4NA5Fz5KWzDJRCFdZi1pTbuznLtqLzxP0NXVwmQwhHONBW7/miPLoMcAXqHX9qpiOUttIbxTJDVzjbKkdUBxhDKlGrWcGjzNF7FIOe2SkTGtFGDK8uXJ/XjMUjJnlCOaUfvy84GSCBMSJyCpLwFIWr15Q8MSjwCxKn5YNsCAXmprjV/xVjBx/cvBiCr3Zd+mREZWkvXw0EjAMuVbo=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 3653ef78-0d0b-403b-e62f-08d77c4f3ae6
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Dec 2019 02:26:42.6906 (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: sjuaWLStrfhcjXdrN7oNpPwL8wpGkwQfoZ3ZjVEgI3CxfTmFwgILBkN0WhgAzgNYcNAhwjElfYIrBIaOefZvLw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR05MB4084
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-08_07:2019-12-05,2019-12-08 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 lowpriorityscore=0 adultscore=0 spamscore=0 clxscore=1015 impostorscore=0 bulkscore=0 mlxscore=0 malwarescore=0 mlxlogscore=999 phishscore=0 suspectscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912090020
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zgIQRiN82I9sbFDcqij2kH5SDJU>
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: Mon, 09 Dec 2019 02:26:52 -0000

Hi Adrian,

If the destination node can process Routing headers on the fast path, but does not recognize the SRH, it SHOULD:
	- skip over the SRH, because Segments Left is equal to zero (as per RFC 8200)
	- forward the packet at line speed

If the destination node cannot process Routing headers on the fast path, it will:
	- punt the packet to the slow path
	- skip over the SRH, because Segments Left is equal to zero (as per RFC 8200)
	- forward the packet, albeit slowly

                                                                                         Ron


Juniper Business Use Only

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Adrian Farrel
Sent: Saturday, December 7, 2019 12:44 PM
To: 'Tom Herbert' <tom@herbertland.com>; '6man' <ipv6@ietf.org>
Subject: RE: What is necessity for SRH, and other EH, insertion/removal?

Hi Tom,

Thanks for breaking the thread and focussing us back on technical questions.

I can see some small value in PSP just as there is in MPLS PHP. This arises in the combination of two circumstances:
- The destination node is not SRH-capable
- The source node and/or the node that determines the SR path is not aware that the destination is not SRH-capable In that case, the penultimate segment end point can know that its segment neighbour end point is not SRH-capable and can perform PSP.

Whether this is ever the case with a central controller is unclear.

I'm not sure that this is a big use case, although MPLS PHP has proven to have use cases as a form of "pop and go" especially when the next hop needs to process the payload as "native".

There may be other use cases, and I'd be keen to learn about them.

The principle of keep things simple yet extensible would suggest that if there are no substantial reasons to include a function it should be shelved until there is a use case, but that this should be done in a way that allows additions if necessary.

Cheers,
Adrian

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Tom Herbert
Sent: 07 December 2019 17:17
To: 6man <ipv6@ietf.org>
Subject: What is necessity for SRH, and other EH, insertion/removal?

Pulling this out into a separate thread. Pertinent questions are:

Why is extension header insertion and removal at necessary?

Why isn't the proposed alternative of IPIP encapsulation sufficient?
(where the encapsulating headers contain the extension headers that would otherwise be inserted)

Please note, I'm asking for the technical justification of the protocol design, saying that it's necessary because it's already being deployed isn't useful in this regard.

Tom

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!WzZKN3lbJ3IPeRv55moUERJbxW2t8ERi7n1WUHmRTQTT1SP56_ODQLQ5_06G_k7T$
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!WzZKN3lbJ3IPeRv55moUERJbxW2t8ERi7n1WUHmRTQTT1SP56_ODQLQ5_06G_k7T$
--------------------------------------------------------------------