Re: [spring] Separating issues (was Re: We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping))

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Sat, 07 December 2019 10:03 UTC

Return-Path: <ketant@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 3EAEA120133; Sat, 7 Dec 2019 02:03:32 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Pgd1PoF1; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=xMv9BGff
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 sVt5jSxKGTfo; Sat, 7 Dec 2019 02:03:28 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7332B12013F; Sat, 7 Dec 2019 02:03:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19924; q=dns/txt; s=iport; t=1575713008; x=1576922608; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CE6g63lMxq/JseiNQd8kAa36jvJQZzJDNotA4BJ2k1U=; b=Pgd1PoF1sLzHGh3hVBFPEZBXVFUBomrCyfuAvEM8rBYCLuMNNAt0FMWz RK8QrpDf8gZAanKu/i2hIOYy/JsRY89IT+ktrhr4CVgVzOuDv1FsrJctx xZljrwmg9sXwR8iZqJ10wm1Y3eS1owbuApZS5Q8m4Kl8ZNsPgQy5I1yA0 s=;
IronPort-PHdr: =?us-ascii?q?9a23=3AAlkKwxHhBvvq5brUqLnqMp1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4w3Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+ef3ncyU8AOxJVURu+DewNk0GUMs=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DFAADUd+td/4cNJK1lGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF+gRwvJCwFbFggBAsqhCyDRgOLAYJfiVuJSIR?= =?us-ascii?q?iglIDVAkBAQEMAQElCAIBAYRAAheBfiQ4EwIDDQEBBAEBAQIBBQRthTcMhVI?= =?us-ascii?q?BAQEBAxIRChMBASwLAQ8CAQgRBAEBJAQDAgICHxEUCQgCBAENBQgagwGBeU0?= =?us-ascii?q?DLgEOoCsCgTiIYXWBMoJ+AQEFhRcNC4IXAwaBNowYGoFBP4ERR4JMPoIbSQI?= =?us-ascii?q?CgUEBASArCYJaMoIskCeFUJgjQwqCLocjhSmEfIQ5gkKXcIQ/iguBRYcAgha?= =?us-ascii?q?PUAIEAgQFAg4BAQWBaSKBWHAVO4JsUBEUjGY4gzuFFIU/dAGBJ44bgVNfAQE?=
X-IronPort-AV: E=Sophos;i="5.69,287,1571702400"; d="scan'208,217";a="679679371"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Dec 2019 10:03:26 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id xB7A3Q28000820 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 7 Dec 2019 10:03:27 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 7 Dec 2019 04:03:26 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 7 Dec 2019 04:03:25 -0600
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 7 Dec 2019 04:03:25 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=E2rborIgps6aF55vwnc9gW5slGGHuSdlSVh7Ta3aPzX87btbbbemHBnbK+4t3slWdXpkZR1obaMoxWrXUDkym0nqrUg8OHaeoTe7Sg/2H10FqrDH9iIt5C5DXYIk7muJpmMct+Q6KqaoZCJ+M3BSeM7E5Xb/OKhgPnBDRxvLN3XGdmLA5J2XTAXEh+LFPSO2puSJS4ALS7ryMolrocVF1Tkx1muR9p5uvu/CVA4xV0ewbwfA3oqxd3BEcCSJZJS6LuylK95ugeHJHhj5Mx8A2lqSuDamYey+jvfykNzXe5NZDLW7KY9nXPvXwDmc3ubENWzfsY+ZKCvkcg0mhzh9bQ==
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=CE6g63lMxq/JseiNQd8kAa36jvJQZzJDNotA4BJ2k1U=; b=BOJQUFsTILqPOXHCfqn0P/+RP7gSywumVKi+cptz+OYn6qkfHr85v7jS1kii6UP81LO9IHBc4DFwaWvGHChzrK8hzFhZzMr/IGrnPfd3YZESu0XgJQcoolxsn+1bIhLlkg2AGX2sDqDrZ7OLsnRa5cD+woXTgQ8LUm8oS8yYGFOrfw3TaiRBPG7Wf0W+BDMhZ8NEglUcLbH071ZZb4GrVBF2cMI2gwM6OWofeixCZQtvgQ4Rv+TKjQz2PQJNJjvH4Z88yRsLnigLsmeuW1ZpDgWFJ4bPaWY14sSnlu7G6XQQmL8k/a4BpeJzrZ28PaXj0fSEkkt0ASNQYNIHwFRpDA==
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=CE6g63lMxq/JseiNQd8kAa36jvJQZzJDNotA4BJ2k1U=; b=xMv9BGffn1lSgHTAIAFVehcX8HQR7pTwgwHqF+yA86r32PiQBdoHTs8aDHcFFM09mbM0vXuD2sQjs1IQF7aqXeZSDhMDbqF8JXQpVyShxNQCDCCFQd5TF3swMiiEYg1iPnPE0ltg+r66G1Lig0VZ8+oUBEd26qT8Z7IAmeRHnYc=
Received: from MWHPR11MB1600.namprd11.prod.outlook.com (10.172.53.142) by MWHPR11MB1871.namprd11.prod.outlook.com (10.175.54.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.14; Sat, 7 Dec 2019 10:03:24 +0000
Received: from MWHPR11MB1600.namprd11.prod.outlook.com ([fe80::8a0:f6fc:426:8b5d]) by MWHPR11MB1600.namprd11.prod.outlook.com ([fe80::8a0:f6fc:426:8b5d%4]) with mapi id 15.20.2516.014; Sat, 7 Dec 2019 10:03:24 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Suresh Krishnan <Suresh@kaloom.com>, 6man <6man@ietf.org>, SPRING WG <spring@ietf.org>
CC: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "int-ads@ietf.org" <int-ads@ietf.org>, rtg-ads <rtg-ads@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Fernando Gont <fgont@si6networks.com>
Thread-Topic: Separating issues (was Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping))
Thread-Index: AQHVrM30iCF9GQ2WD0KW/SnLVpzfRaeucM+Q
Date: Sat, 7 Dec 2019 10:03:24 +0000
Message-ID: <MWHPR11MB16002C07CE596EACDA0CF7ABC15E0@MWHPR11MB1600.namprd11.prod.outlook.com>
References: <f2a0ad13-0eba-6f5a-1d3c-e45e2780f201@si6networks.com> <D666EA6E-E8E9-439A-9CDE-20857F03CB65@employees.org> <4255AD3B-379C-45BF-96E1-D3D9141A684F@liquidtelecom.com> <d59de54e-c7f8-be67-1e77-b051735d40a6@gmail.com> <3bce7b18-ea45-d29f-5dfb-1d3258b07d1e@si6networks.com> <c6e1f690-b0bf-9f45-8fa7-92ed182c5b04@gmail.com> <a2cc5cbd-ac06-e193-307c-3ffe5b21b0b1@si6networks.com> <C17FBA5F-A2C1-48C0-B668-F387D9E4C1C2@kaloom.com>
In-Reply-To: <C17FBA5F-A2C1-48C0-B668-F387D9E4C1C2@kaloom.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=ketant@cisco.com;
x-originating-ip: [2405:201:1800:c766:f042:eb72:602c:5767]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c8e0cf6a-7c3b-40be-c536-08d77afcb2be
x-ms-traffictypediagnostic: MWHPR11MB1871:
x-microsoft-antispam-prvs: <MWHPR11MB1871B86F0552171361FA01DFC15E0@MWHPR11MB1871.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0244637DEA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(136003)(376002)(346002)(396003)(189003)(199004)(53754006)(53546011)(316002)(6506007)(54906003)(110136005)(33656002)(5660300002)(102836004)(478600001)(186003)(966005)(74316002)(86362001)(2906002)(790700001)(99286004)(76116006)(66476007)(4326008)(64756008)(66946007)(66446008)(66556008)(76176011)(8936002)(8676002)(81166006)(7696005)(229853002)(81156014)(9686003)(54896002)(55016002)(71200400001)(71190400001)(52536014); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1871; H:MWHPR11MB1600.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: a5H/QJyt1lXtSDRqwxkk5kJJTL+iB40oR9mBoDPZ5WS50fmQAZZwp6RUQZ01WtwUYGXXqUnwsxC40RaXVmSZe9eKDEjMf2ElJzFuSwrofQxyc3jdIGD4qwMEUabFmBG1EpWSuDanOQtHeg88DGJc3JbYJKXE3dzymPS4ftZVKSP9AWvJhleR4MNH7OqAUYf2O2N1O7vb6P/Y/zBLeACpgGvZu6nBeiBEBF67iDMUMaGIU9Vdk1EqoNYxDNiGVGne4iiV1i24OfjCocCYQISx2vx9u4eVLr17PSrl2ub4FAfi65y0M/g7g1suHsCm9tnaj3EqDs+C21ORjQ+6hB4SFkCwbQb+wW77mOBlUXhbeWeQ/4ehYkeAl3KFIwmWXOtFpgYrJmheQ2RfnM4k9h88f8KXOVTZyPTFN804vkgKnG0m6Etz6WHn6vv703T2QsJ8PTca2LfgDTYufPOLMNL3+lPqEzNfXdBOuh5C+vuvmwbQ1c+sUYabNBbhwQWYd6UhqC5Ke/ss+rguDTgeFFW3H+Q0JmA5FAE63JKPGQvLQ0g=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR11MB16002C07CE596EACDA0CF7ABC15E0MWHPR11MB1600namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c8e0cf6a-7c3b-40be-c536-08d77afcb2be
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Dec 2019 10:03:24.4159 (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: ORn5j0tRh3UP+dDNmBNdsD9M738o0JJ7KOhkmi5mk90t+46cgN+Vjul466z6wwogsYgaEthnhkEmr5QE0bzv5w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1871
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/mlMap2cDYR50l_MxOY3IW6RQkIU>
Subject: Re: [spring] Separating issues (was Re: We don't seem to be following our processes (Re: 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: Sat, 07 Dec 2019 10:03:32 -0000

+ 1 and I will also clarify, what I see as, a misunderstanding (or perhaps a misrepresentation) of the PSP behaviour on the other thread that Suresh has started.


From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Suresh Krishnan
Sent: 07 December 2019 12:44
To: 6man <6man@ietf.org>rg>; SPRING WG <spring@ietf.org>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>rg>; int-ads@ietf.org; rtg-ads <rtg-ads@ietf.org>rg>; Bob Hinden <bob.hinden@gmail.com>om>; Fernando Gont <fgont@si6networks.com>
Subject: Separating issues (was Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping))

(Apologies up front. I am about to get on a 10 hr flight and will be unable to respond for at least that period)

Hi all,
  Picking the last message in the thread to reply to. It looks to me that there are at least two different (but related) issues being discussed here

a) Spring SRv6 NP behavior (related to the WGLC of that draft)
b) The Header insertion drafts and how to deal with them

I really think that

a) should preferably stay in the spring ML and a pointer to the discussion sent to the 6man mailing list would be in order
b) should preferably stay in the 6man ML

I think the communities for the two drafts are different and I think the discussions can be more focused if the issues are addressed by the relevant wgs. As to what happens if the spring draft hits the IESG and contains text in violation of RFC8200, I had already sent my thoughts about this back in September

https://mailarchive.ietf.org/arch/msg/spring/uA-WxxgBJeMu65SkrKCTL5BJMcU

with the relevant text

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

*In my view*, the authors of the SRv6 NP draft have made an effort to address these violations by removing the header insertion from the draft. We can continue discussing whether penultimate hop popping constitutes a violation on the spring mailing list (I intend to respond to Fernando’a mail there).

Thanks
Suresh


On Dec 7, 2019, at 11:07 AM, Fernando Gont <fgont@si6networks.com<mailto:fgont@si6networks.com>> wrote:

On 6/12/19 23:47, Brian E Carpenter wrote:

Again, comment at the end...
On 07-Dec-19 14:37, Fernando Gont wrote:

On 6/12/19 22:15, Brian E Carpenter wrote:
[...]



and if such a thing is required, an update to RFC8200 should be done.

Why does that follow? Alternatively, draft-ietf-spring-srv6-network-programming could acknowledge that it deviates from RFC8200.

You can deviate from s "should", not from a "must". This is an outright
violation of a spec, rather than a mere "deviation".



Whether that's acceptable would be a question for the IETF Last Call rather than any single WG.

I would expect that a WG cannot ship a document that is violating an
existing spec, where the wg shipping the document is not in a position
of making decisions regarding the spec being violated.

That would be like a waste of energy and time for all.




At the moment, the draft only mentions RFC8200 in a context that discusses neither insertion nor removal of extension headers, which is beside the point. Like draft-voyer, if it describes a violation of RFC8200, shouldn't that be explicit in the text?

There's a lot of jargon in draft-ietf-spring-srv6-network-programming. I can't tell from the jargon whether "insert" means "insert on the fly" and whether "Pop the SRH" means "delete on the fly". Should those terms be clarified before the draft advances?

Well, if it's not clear to you, it would seem to me that the simple
answer would be "yes".

But if "insert" refers to the encapsulating node at the SR domain ingress, it's no problem, and if "pop" simply means doing normal routing header processing, it's no problem. It simply isn't clear in the text, at least not clear to me.

The fact that a folk that has been deeply involved with IPv6 cannot
unequivocally tell what they talking about should be an indication with
respect to how ready the document is to be shipped.

(pop when you are the destination but SL!=0 is essentially 'in the
network removal')

THanks,
--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com<mailto:fgont@si6networks.com>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492