Re: [spring] Question about SRv6 Insert function

Ron Bonica <rbonica@juniper.net> Mon, 02 September 2019 20:58 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 067D31200B2; Mon, 2 Sep 2019 13:58:41 -0700 (PDT)
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
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 DtfhlwyOfv18; Mon, 2 Sep 2019 13:58:38 -0700 (PDT)
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 69CA012004A; Mon, 2 Sep 2019 13:58:38 -0700 (PDT)
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 x82Kvv4F030794; Mon, 2 Sep 2019 13:58:29 -0700
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=JAWsoKzvCZAbCqm8O4RGNbqJ3XcNyM2EX71g9deK5Fc=; b=W0eoUQ4PmFUcEd2zR5bG2mVy64UO0xppk7iJkLklYDd0p4XhWSppOagBuzrW9u9WEhAW GIWryvJZHZ8siIEgGQIMrIrE0zJe8uIGlOPtdF8qKEv0xyMVoAyJKGECbxNqQSAOZd1N bfQefW2Nl0c/11BakkXmRaTy4aPl40ktbH8dprdIhdiSZxIVx3P5fcc0EKgEPe7DgmsU i5c5RBwVTFteTFnuc2Ebb2YRw7Fw/3nFpYJX7YO2UKeLY/y7JQ4sqOlb4Ru2k7vo1uqg xf4mYqodixJMcNil3XjXkxk2iWqseGvQG5EzgTq6YGyn//QjxhmvG38R2h00OwIWKU3v fw==
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp2058.outbound.protection.outlook.com [104.47.40.58]) by mx0a-00273201.pphosted.com with ESMTP id 2uqqwn3d64-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 02 Sep 2019 13:58:29 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HxVeGPZ3bW5PVlGL3W97sWWMoYG62rHDVilqmCXqvVdEb/DHJGm1dwkZATGWsn3w4FuVh/C/5NtlR3qEfWjNT5WegmlcgpfGcU3oCUB28N1KzGfHiCkZugtA4SoU+QMIKqltrKYpNhWV9WJpZR3tp8WAcATSdzbk5ghKYAOIAeM5UMWbxx0raEwZYjSnVBoCdSrXiaaBN2hvYiU82zuX6zgs/fOIVQG9zUK0AI8ScNGHvoI6YUUjrLrYrRTJsRlqFzM9FFVxUULbpF0UX/7/Hgt9kUP0ZrUc/GPWoS7jSxHNLAuKDieiIKMe6nHhny5DJYA1cukybrK5E8FUdsBKeQ==
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=JAWsoKzvCZAbCqm8O4RGNbqJ3XcNyM2EX71g9deK5Fc=; b=Ck+1rgS3QxGRDIz8KW1EvPuXCUswK1Gy3NapgBfVVQRgUeSifZyBGJGXqeKEYdJ1rPLG9/YSGmyK9WVacUk6rKJB1Q5iB1O4OsizKmgVD1U4i3uupU234Peowikz/w5A6B+2daupFgrCzfGWBJkZWIlJeLjFCnAAVWKm8drT0tQsSBLPhJ4gPI05qwVLlPpBTBcIe18r3RrvMy6iEFLkz8KxK/yNX4S+JVspt09BikovL6sEzwrHG80HRhP53oINX3ARdRQADScsr5D4jwFFPaytnaAlvqeA2E5XXNTxBPA6mHuuv7kMOXwDej282+QnKzoM/cqfqIGPtIRbb8Q6yQ==
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
Received: from BYAPR05MB5463.namprd05.prod.outlook.com (20.177.185.144) by BYAPR05MB5127.namprd05.prod.outlook.com (20.177.231.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.9; Mon, 2 Sep 2019 20:58:27 +0000
Received: from BYAPR05MB5463.namprd05.prod.outlook.com ([fe80::f4f2:f284:d49a:890a]) by BYAPR05MB5463.namprd05.prod.outlook.com ([fe80::f4f2:f284:d49a:890a%4]) with mapi id 15.20.2241.012; Mon, 2 Sep 2019 20:58:27 +0000
From: Ron Bonica <rbonica@juniper.net>
To: Ca By <cb.list6@gmail.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
CC: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>, draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: Question about SRv6 Insert function
Thread-Index: AQHVYaiGkQrPBxFhV02Y8RCTv8yVq6cYnx8AgAA+72A=
Content-Class:
Date: Mon, 2 Sep 2019 20:58:27 +0000
Message-ID: <BYAPR05MB54639033C12A9FC41FA27845AEBE0@BYAPR05MB5463.namprd05.prod.outlook.com>
References: <HK0PR03MB3970C6DCC635E7CD802D65FDFCBD0@HK0PR03MB3970.apcprd03.prod.outlook.com> <BYAPR05MB54636A2332FED916A26A6F14AEBD0@BYAPR05MB5463.namprd05.prod.outlook.com> <3e31873a-278a-2154-0e71-4d820bba323d@gont.com.ar> <4012D854-2F10-4476-951D-FFFE73C5083C@gmail.com> <CAD6AjGTkwbTAKGDH63pM7Gc3_2BRV98E2MLMrUbjmc09Mcv=Ow@mail.gmail.com>
In-Reply-To: <CAD6AjGTkwbTAKGDH63pM7Gc3_2BRV98E2MLMrUbjmc09Mcv=Ow@mail.gmail.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-09-02T20:58:25.7802031Z; 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=0ea15606-6844-40f7-9993-f63303224a96; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
dlp-product: dlpe-windows
dlp-version: 11.2.0.14
dlp-reaction: no-action
x-originating-ip: [66.129.241.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b45d659e-7e68-4607-0fe7-08d72fe84d76
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BYAPR05MB5127;
x-ms-traffictypediagnostic: BYAPR05MB5127:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <BYAPR05MB51279170305CCE34AFFCE02BAEBE0@BYAPR05MB5127.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01480965DA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(366004)(136003)(396003)(39860400002)(346002)(199004)(189003)(606006)(316002)(11346002)(446003)(256004)(26005)(4326008)(53546011)(5660300002)(102836004)(6506007)(76176011)(86362001)(66446008)(478600001)(66476007)(76116006)(66556008)(53936002)(64756008)(52536014)(14454004)(966005)(2906002)(6116002)(790700001)(25786009)(33656002)(3846002)(229853002)(66946007)(66574012)(6246003)(476003)(71200400001)(71190400001)(486006)(74316002)(6306002)(54896002)(236005)(66066001)(55016002)(9686003)(110136005)(54906003)(7696005)(8676002)(81156014)(81166006)(7736002)(99286004)(8936002)(186003)(14444005)(6436002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB5127; H:BYAPR05MB5463.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: +FWMsdlqoujLStbjteOzNfB2KW8626lSRCjbD0nVAWdksJAB1n/oVDzuSY0sdJzuQG9frumlG+ITads2kTt0nSWXYzX/E2qZQcIOz/jsxmAiv7frEJu0BN3BtvNI5pyW31XTEQ435Xhc6qns0KXZhXhNaz6VHT39VaqTjgnI5SbRjCowk0lgJ616Oj0X/20eK3fGYh4+0ncjjijoILPd9FkRNY6EjKDgZkH3haZHnAhnhNBotIjUMN8kKirgPZg56CA1LlHol3pQ8NBt5wSbyy2UOzqG41DcE8iPaQFwSk23RW+uVQeODIBV8LP0SY+8FMmBvv0I8D58f1G6mRGu5K60+ORas/8rJg87eLejfJsgT2hXmjaJvbYbGobSod8RokW+9n8210w20PGnO1bYisPYZnMDUZEUv9FXrzwLZ+w=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR05MB54639033C12A9FC41FA27845AEBE0BYAPR05MB5463namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: b45d659e-7e68-4607-0fe7-08d72fe84d76
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Sep 2019 20:58:27.3696 (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: P0J2aJhLcuXy2gfq9hFlc6Fw0A/kVlVWm+eNYz8M83vimAPuYYq8qb3rR/UMguu8N/iX7LwLrtVCHG5iZ8PoWA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB5127
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.70,1.0.8 definitions=2019-09-02_08:2019-08-29,2019-09-02 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 bulkscore=0 mlxscore=0 suspectscore=0 lowpriorityscore=0 impostorscore=0 priorityscore=1501 clxscore=1011 mlxlogscore=999 malwarescore=0 spamscore=0 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1909020236
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/_8bjKJoDSwJTWASgnOkUBXtwWHU>
Subject: Re: [spring] Question about SRv6 Insert function
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: Mon, 02 Sep 2019 20:58:41 -0000

Cameron,

I hear you. SRv6+ will try to limit its ask to the following:


  *   Enough community review to make sure that we aren't doing anything dangerous
  *   Four code points (i.e., two IPv6 Routing types and two IPv6 options)
  *   One registry (i.e., Special purpose SIDs)

Beyond that, we will try to keep the noise to a minimum.

                                          Ron




From: Ca By <cb.list6@gmail.com>
Sent: Monday, September 2, 2019 1:10 PM
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: 6man@ietf.org; Fernando Gont <fernando@gont.com.ar>ar>; Ron Bonica <rbonica@juniper.net>et>; draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>rg>; draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>rg>; spring@ietf.org
Subject: Re: Question about SRv6 Insert function



On Mon, Sep 2, 2019 at 9:07 AM Suresh Krishnan <suresh.krishnan@gmail.com<mailto:suresh.krishnan@gmail.com>> wrote:
Hi Fernando,

On Aug 31, 2019, at 10:09 AM, Fernando Gont <fernando@gont.com.ar<mailto:fernando@gont.com.ar>> wrote:

On 30/8/19 20:24, Ron Bonica wrote:
Li,



In the scenarios that you mention, below, SRv6 nodes have the following
options:



1. To prepend and IPv6 header, with its own SRH
2. To insert an SRH, as described below



Option 1 is in keeping with the word and spirit of RFC 8200. As you
point out, Option 2 contradicts RFC 8200.



So, we should probably explore the motivation for Option 2). If the
motivation is not sufficient, we should probably standardize on Option 1.

My argument would be:
Folks would do whatever they please with 1). If somehow they feel the
need to do 2), they should *refrain from even suggesting it*, post an
internet draft that proposes to update RFC8200 to allow for the
insertion of EHs, wait for that to be adopted and published, and only
then suggest to do EH insertion.

I have put down my thoughts on the future of header insertion work in a mail to the 6man list in May 2017. The mail can be found below

https://mailarchive.ietf.org/arch/msg/ipv6/4MevopH9_iQglUizhoT5Rl-TjRc<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_ipv6_4MevopH9-5FiQglUizhoT5Rl-2DTjRc&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Fch9FQ82sir-BoLx84hKuKwl-AWF2EfpHcAwrDThKP8&m=d-vzMZODP_ALHfMhubf5WRxJTGOhRzUKJbOtu85Dffk&s=fbmh6fqc8mAnydHmPoIhor-HPFSjlsvhAIwCflKUbSk&e=>



P.S.: Given the amount of discussion there has been on this topic in the
context of RFC8200, I'd like to hope that there's no draft-ietf document
suggesting EH-insertion or, if there is, the relevant ADs and chairs
make sure that's not the case anymore.

Yes. If a draft violates RFC8200 and it hits the IESG for evaluation, I will certainly hold a DISCUSS position until the violations are fixed.

Thanks
Suresh

Thanks. It sounds to me the the SR folks are re-inventing NSH in ipv6.

The internet layer is a narrow waist.

My humble opinion is SR has the same real market traction as  LISP and NSH, meaning very niche, but loud.

They should look at publishing in the experimental track before asking for the world.

Regards,
Cameron






--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ipv6&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Fch9FQ82sir-BoLx84hKuKwl-AWF2EfpHcAwrDThKP8&m=d-vzMZODP_ALHfMhubf5WRxJTGOhRzUKJbOtu85Dffk&s=CJjpcqScEQwVpIUZyR6cQhyDb5ouN7wH6aIrmCLoIMM&e=>
--------------------------------------------------------------------


Juniper Business Use Only