IETF Logo Mail Archive

[spring] Spirit and Letter of the Law (was: Question about SRv6 Insert function)

Ron Bonica <rbonica@juniper.net> Wed, 04 September 2019 18:28 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 4980A120BBE; Wed, 4 Sep 2019 11:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, URIBL_BLOCKED=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 7CZsAEpsxewi; Wed, 4 Sep 2019 11:28:05 -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 163B4120BC5; Wed, 4 Sep 2019 11:28:05 -0700 (PDT)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x84IOVQb004159; Wed, 4 Sep 2019 11:27:57 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=NuLltziRAKzKCFot+feaOGfXx7eueKUeT5IrWH64cY8=; b=OTQInfw4DBKB2Bxte1fg7Xmn/fjMvhTOch8qPE6xgcksws5oal9pM1q7dfenHieQeITk 9vVSM9qP7kJoCvNaqhJVgoO3rseKOPcqwlDI89uHlxQtpDaGFNoTkavFhn1VndVfiF3C AO+RmhgzhXzIsYkBkmn/6vJBAfq0HHQQ3pXk2T4DTJ43WdgyhTE+ICbCyKuaVYMWmJ6I j9IDfuQ551Alfd6JlslPJyvAWcIuGXlro+IcEa9WhTHmzT25w6KvO8zHzoVYucFF7rro azkWPmS3KzBx5co7UBjjoQz6P+qc+YdrCEv20oscEQY4wwWqltVJ4RyI6l6N2O+ybL+W Dw==
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp2059.outbound.protection.outlook.com [104.47.40.59]) by mx0a-00273201.pphosted.com with ESMTP id 2us7ap474p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 04 Sep 2019 11:27:56 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=N9K1X8NI3J6pnBEoqfxcowpofjRsqnjeYMn/BU7X0aG64JFt5PtJhtjcJzKx4ou4DBDjOJljrPAqZ+8yz5TBsd8v3U/Q30+Sl/y5hFcnd+2uAJOBuiCz+w1nIIEvuAayrdloIM+uVDRxjvrvnUB+bCmC5c/CCgPVRjTFKQgyLc3YN63Uxgmv8x18h/olJPe+/5fGZnR1J5VRUfBNkkEW+McNrwoeNIX7D+kGeFdSCwVB1liu5k3R6AbM0E8X4GixIz06F7TyrKfLvxY3cDkuNOtIKvsw6w/gBGzc81cNtt0S25cmCrINTrOPCk3xkF0JpO36qIvVPwkue9K94ujXxQ==
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=NuLltziRAKzKCFot+feaOGfXx7eueKUeT5IrWH64cY8=; b=CLmkWA9eYoZqMJ2eOcDdS4/Prikay7DJpdcS0bgJdKnhIkf5+2DmXGNtyqmwS2/RThAbHmvRmUNvqPlatiV2VA+gbt1omd/Iy/DbJVTgBHD8/8CkrOm94bLlkA4jF0AjblUR+Sp04lRpsTjIL8bBevoNtFKd2svNcriwTO+VrCaenSgHTg8I1+g7DbXZnwVElFvJYuVWgE4Y4KlXHq3H6dMchNBe8qOpoGj8R4s7KAhQooZJwsKJNgkJHImfxUYrveVCaPTu+JnsoQs/C5pJqVkySLNWxroRc5G6g6Prr0E0LJ0FRrXMKsUHyQV8bOVnxRdvLrJF0mb14KZYCbMzqg==
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 BYAPR05MB6549.namprd05.prod.outlook.com (20.178.234.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.12; Wed, 4 Sep 2019 18:27:54 +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.014; Wed, 4 Sep 2019 18:27:54 +0000
From: Ron Bonica <rbonica@juniper.net>
To: Ole Troan <otroan@employees.org>, Fernando Gont <fernando@gont.com.ar>
CC: Suresh Krishnan <suresh.krishnan@gmail.com>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Thread-Topic: Spirit and Letter of the Law (was: Question about SRv6 Insert function)
Thread-Index: AdVjS14TVsuRj78sSeu1r8rfsn3VOQ==
Content-Class:
Date: Wed, 04 Sep 2019 18:27:54 +0000
Message-ID: <BYAPR05MB54637FEAE1518F83977D274FAEB80@BYAPR05MB5463.namprd05.prod.outlook.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-04T18:27:52.5331331Z; 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=2fd718f7-a72e-4cda-af69-639a0b2563ae; 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.12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9e048d66-1b26-42dd-79a4-08d731659a49
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:BYAPR05MB6549;
x-ms-traffictypediagnostic: BYAPR05MB6549:
x-microsoft-antispam-prvs: <BYAPR05MB6549B7EADEBD900252618F8BAEB80@BYAPR05MB6549.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 0150F3F97D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(346002)(136003)(376002)(366004)(39860400002)(13464003)(199004)(189003)(51444003)(476003)(8936002)(71190400001)(66066001)(6116002)(71200400001)(25786009)(81166006)(110136005)(99286004)(53936002)(3846002)(486006)(81156014)(2906002)(7696005)(5660300002)(6436002)(64756008)(305945005)(66476007)(14444005)(66946007)(4326008)(102836004)(66446008)(9686003)(55016002)(26005)(256004)(53546011)(6506007)(52536014)(54906003)(86362001)(33656002)(186003)(14454004)(478600001)(76116006)(316002)(74316002)(8676002)(66556008)(7736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB6549; 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: KnXwg0tsVtKMoV/WGJhbkb32nEFkuq3sfJWwwW1ITaIbWnIvTU/yOJKtuhvrFQlaB5xb+wxDrKgJnfm0amoujb8qFmqq+YA5nDGx5zX3kEX5WaAh62f1fY/2AkgGnnZrzQ+M4WdQDEnQIywKq9VAsEs2LkB9x6ocGwVVxqPPzjgZ1OeHMpn3Nb+XUGE/dfQrchhVunJdMlfliEqoxjcreQ/hN+C5ERMoYC3Ap/+wkgSOfoZVSdkSkKl+ha01WHWjwUUsvk2pj8y6/CezvKFRZwSf0a5QBhzge/BAW1Mhk44gYssqGAGhL6Uc4+2xViTlqlvNoi6LgXWvHJ1sFAYDvEvzyjlDrTOSdoQ+vHo+XzjjVkl6+V6aX/IWfxqi+JOQ/jOu/8n7r4OvJGjDGL0ZSV1KOCUq21LGL5A5F19kC9s=
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: 9e048d66-1b26-42dd-79a4-08d731659a49
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2019 18:27:54.4539 (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: A/A6H9f6SiteYPfekoA5eNYSbG3jUZQEDPK5Y8ciVs/vn/czXtVdN/FXPgrGIalTHkIMVkWdz8tQPm2oIfh1hQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB6549
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.70,1.0.8 definitions=2019-09-04_05:2019-09-04,2019-09-04 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 malwarescore=0 lowpriorityscore=0 bulkscore=0 mlxscore=0 impostorscore=0 spamscore=0 priorityscore=1501 suspectscore=0 mlxlogscore=999 clxscore=1015 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1909040183
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/GNnOambnCovorfVBko8wr9wgjlo>
Subject: [spring] Spirit and Letter of the Law (was: 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: Wed, 04 Sep 2019 18:28:08 -0000

Ole,

Yes, a deep breath and some introspection are always a good thing.

First, I think that we need to make a distinction between the "spirit" and "letter" of the law. Next, we need to make a statement regarding good engineering practice.

RFC 8200 mandates some things. For example, In an IPv6 header, the source address must precede the destination address. Any attempt to reverse those two would violate the letter of the law.

By contrast, RFC 8200 strongly suggests other things. For example, transit nodes should not insert or delete extension headers. In general, these suggestions should be heeded. But exemptions can be granted, on a case-by-case basis, given that the motivation is strong, the risk is minimal, and there are no viable alternatives.

For better or worse, RFC 8200 does not use RFC 2119 language. So it is difficult to distinguish between the spirit and letter of the law. I think that is the genesis of the current debate.

Beyond that, we need to make a statement regarding good engineering practice. If a technology violates the spirit of RFC 8200 once, with good reason, that is fine. If it violates the spirit of RFC 8200 twice, we should all start asking questions. If it violates the spirit of RFC 8200 three times, and promises to do so again in the future, we should start to question whether that technology is building on RFC 8200 or trying to redefine it.
                                                                                             Ron



Juniper Business Use Only

-----Original Message-----
From: Ole Troan <otroan@employees.org> 
Sent: Wednesday, September 4, 2019 2:58 AM
To: Fernando Gont <fernando@gont.com.ar>
Cc: Suresh Krishnan <suresh.krishnan@gmail.com>; Ron Bonica <rbonica@juniper.net>; spring@ietf.org; 6man@ietf.org; draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>; draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: Question about SRv6 Insert function

[ snip ]
I would prefer that we calmed down a bit on the protocol policing.

[ snip ]

v2.23.0 | Report a Bug | By Email