IETF Logo Mail Archive

Re: [spring] Thoughts and concerns

"Bertrand Duvivier (bduvivie)" <bduvivie@cisco.com> Fri, 29 November 2019 10:07 UTC

Return-Path: <bduvivie@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 970F81208F8 for <spring@ietfa.amsl.com>; Fri, 29 Nov 2019 02:07:19 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=EYzL1Ctw; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ZyAQZ03R
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 pwcOyyS6rbKW for <spring@ietfa.amsl.com>; Fri, 29 Nov 2019 02:07:15 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E53A11208F9 for <spring@ietfa.amsl.com>; Fri, 29 Nov 2019 02:07:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17773; q=dns/txt; s=iport; t=1575022035; x=1576231635; h=from:to:cc:subject:date:message-id:mime-version; bh=fKWE84bljJPuZKGiFbtlpQXpdHwnYwjTdYvOsyp2W9g=; b=EYzL1Ctw0J5TN+wEfiVQtZFiUnv1h/trYBqGW7/4EDkoVVQ3Yf8riFjS UKA0GmwItt0B3IspFYaRLFZGTZ4OnMP/1sgc9dx4lv9qdjVAMB4pPuGoK qoPn6UGqFSEYM4xtsix9ppR0GKjwE85Hj1SF8p6BrwztAobLP1Djxqdtd w=;
IronPort-PHdr: 9a23:+9Ll7hOtMUzIJ7hyE9Ml6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjxIOP0bjI7EexJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DhBQAo7eBd/4oNJK1lHAEBAQEBBwEBEQEEBAEBgX6BHC9QBWxYIAQLKoQrg0YDim6COpNHhGKCUgNUCQEBAQwBASUIAgEBhEAZgXMkOBMCAw0BAQQBAQECAQUEbYU3AQuFUwIBAQISCwYdAQEsCwERAQhCAgQwJwQOBSKDAAGBeU0DLgEOp1ACgTiIYHWBMoJ+AQEFgTUBAwOBDoJXGIIXAwaBNowWGoFBP4ERJwwUgkw+gmQBAQGBeRaCYzKCLJAahUyJSY8TCoIuhx6FJ4kUG4JBl2KOSoFChnqRWwIEAgQFAg4BAQWBaSKBWHAVOyoBgkFQERSIVINzhFk7hT90ARCBF5A1AQE
X-IronPort-AV: E=Sophos;i="5.69,257,1571702400"; d="scan'208,217";a="670242475"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Nov 2019 10:07:13 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id xATA7DsZ018059 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 Nov 2019 10:07:13 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 29 Nov 2019 04:07:12 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 29 Nov 2019 05:07:11 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 29 Nov 2019 05:07:11 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SYiPwNVQzyFp3kWgCM/rbLXw2rLG/QsBkdbghVtI2RClOLYjpF/T47YnvkXdJHCth3ZuIScL3yVn77qvKKFveA8NxAKIIJKC3VTaNO687p6PZxBV84iQIlIISYtT/SZAW1ugF9NSGUarXKzW4QqIZ5Ig9S68qWb32ObyiFvWrbF16IgdMB0hussSh4pOgAWnpTiEeJ3/OI2TqU8Jn7NqljtW/jOUqrrgORxftAskLX/jyTO2mfKYxMosrS/JAiJKc4h3k77Wbqwdy5MLYVO1xlse6Ok6rh5gfSix6EkO4DH2m7Erw4NfbwrxZ49DRkZKeW4yspPS5bR+VaUOPwkK+A==
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=fKWE84bljJPuZKGiFbtlpQXpdHwnYwjTdYvOsyp2W9g=; b=it2jBJXOuyc/ok1owwFs5ZzsaZtoi3TlMOWrPMj4rRWJJLbz55VMSfNMTzv+Q1Ux49FV91jzkhaze/mHSBggW8nFovbQ0KTLFRc7TcdUzIe6+zCewUAQn8ps21ZSkEcjub2Ue2JsuoksbqFNy1CVbT5Q0xxgEBuDUZv5VQLnUx0UQyNXGeIa3AeFWw+PFFwJPIqobMfAPHlK9Ww90Gw0ktdMDpyrmHeLcGPx1rPgULRXjzldX3lZ8L4ysv4OBUsdb+jl2sFnYvCYgKgQ8kl/hGnV9S6ImS4OeiMjhmarjoxJAC5LvIlKn+ZAcnKqg3DrAwv1QyV4HvPFkshCyVNNnA==
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=fKWE84bljJPuZKGiFbtlpQXpdHwnYwjTdYvOsyp2W9g=; b=ZyAQZ03RfMKI1plwULACyGCGN77ZyCBIppLP48XZNFIdnbIaOS4h+TSz7mUvRDC+WJjNeP5Cnpv/MZqpvNCHULuSr6w5lniPz0aXeHdiwoIMHkEnuCTYa1IGWezq8An/5+58BvSIbCBu4NE9W3tXBAlF8PG+GC0jukAVTYirRmQ=
Received: from CY4PR11MB1238.namprd11.prod.outlook.com (10.173.17.17) by CY4PR11MB1815.namprd11.prod.outlook.com (10.175.80.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.18; Fri, 29 Nov 2019 10:07:10 +0000
Received: from CY4PR11MB1238.namprd11.prod.outlook.com ([fe80::d47c:b5d4:5ba7:e73]) by CY4PR11MB1238.namprd11.prod.outlook.com ([fe80::d47c:b5d4:5ba7:e73%11]) with mapi id 15.20.2474.023; Fri, 29 Nov 2019 10:07:10 +0000
From: "Bertrand Duvivier (bduvivie)" <bduvivie@cisco.com>
To: "spring@ietfa.amsl.com" <spring@ietfa.amsl.com>
CC: "Andrew.Alston@liquidtelecom.com" <Andrew.Alston@liquidtelecom.com>
Thread-Topic: [spring] Thoughts and concerns
Thread-Index: AQHVppzDvdY+8qJ9oEqrLLnsSE2+Lw==
Date: Fri, 29 Nov 2019 10:07:09 +0000
Message-ID: <FBE0C15E-FB2E-4195-A60B-3CB2D87209EC@cisco.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=bduvivie@cisco.com;
x-originating-ip: [2a02:a03f:c0f2:3b00:21a8:dd7e:3fdf:15c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2389d9f6-5438-44e0-92e1-08d774b3e5f0
x-ms-traffictypediagnostic: CY4PR11MB1815:
x-microsoft-antispam-prvs: <CY4PR11MB1815A2DE2951AF6FA9300704D6460@CY4PR11MB1815.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0236114672
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(396003)(39860400002)(366004)(136003)(346002)(189003)(199004)(14444005)(5640700003)(81166006)(6512007)(46003)(8676002)(186003)(1730700003)(81156014)(7736002)(86362001)(58126008)(2351001)(316002)(71190400001)(256004)(25786009)(2616005)(8936002)(478600001)(6916009)(966005)(2501003)(14454004)(71200400001)(99286004)(2906002)(91956017)(33656002)(66446008)(64756008)(66946007)(6436002)(6506007)(76116006)(229853002)(6116002)(102836004)(5660300002)(66556008)(6246003)(66476007)(6306002)(606006)(36756003)(236005)(4326008)(6486002)(54896002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1815; H:CY4PR11MB1238.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: 6r2OWmrvkeqAw7p7OpFFdpvW6eD3dUH1cvqMPNQE9nKQptbs+qdyOpBsFVpO8QY8m1+JxPK2XBw7l71jtsed6+Vq9px3bEAiuZdVZURWAiOpxZUKGWwamM2fizgibViyU3EPdHDUqw+ri3TmOvSolTRAJHDBaE1FE7jDjLhMVNAqHYcRBen3PqTYERdu6J7+JrKnd+R2ZIPj6lajubfvDYL3hXcvY33smF0gPGiNctaUzjgD6JS0CcjuJnqlZjYYA/+V70iEZtTrtCU0pifitStM2v8/+VTzmB1u1BqvFbZAKf2ssfzeF8FfNWzBDMl6mb9Q5o18WjiTIsB33fwbWaPeeDXdnls6S7FraqSs/9BQMxnuBRW9WV+xNnCFivfB8KSQhFlkADRmYI3+EGyi5jfz1XKeehL/FVIXPHawmAZFfZWKLt/scBTBO7w5VaPeWi3B2BnJxp5C8UOgnwTIaAtt/8RB1nCmde1LkUofV2M=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_FBE0C15EFB2E4195A60B3CB2D87209ECciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2389d9f6-5438-44e0-92e1-08d774b3e5f0
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Nov 2019 10:07:10.0281 (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: ZSappOen6wNB6Kn4a+lPYE2scoR1cZ929twNZhBJnpW/scttfTkhEeZGJ8CNvO3g2qkxew+Ln3+OODrmK1aDRw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1815
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xch-rcd-006.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/xQr9DLihrK-P00X5jBs4lOKumrs>
Subject: Re: [spring] Thoughts and concerns
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: Fri, 29 Nov 2019 10:07:20 -0000

SRING WG chairs and members,

If this is not an IETF Business (like suggested by Andrew Alton), I do suggest this irrelevant threat to be abandon/drop from the IETF SPING mailing list.

BRGDS Bertrand

[spring] Thoughts and concerns

Andrew Alston <Andrew.Alston@liquidtelecom.com> Thu, 28 November 2019 15:26 UTCShow header<https://mailarchive.ietf.org/arch/msg/spring/WEMigLTseVvQ2Ke_GdycuI7sHKk>

Hi Guys,





I have some questions - I ran across a document which has me deeply concerned - that purports to be written by the authors of SRH and makes direct reference to this working group.  And since the claims in it are deeply worrying - I think its time to ask for some answers. I fully realize that well - what people publish outside of the IETF is probably no business of the IETF - but, a document that claims to be published by the authors of a draft - that makes false claims about the working groups very charter - that - concerns me.



The document itself can be found at: https://www.segment-routing.net/images/20191029-02-Update-on-SRv6-standardization-activities.pdf



Now - here is my issue



Firstly - the second bullet point in that document runs *DIRECTLY* contrary to what is stated in the spring charter - to quote the charter:



The Source Packet Routing in NetworkinG (SPRING) Working Group is the home of Segment Routing (SR) using MPLS (SR-MPLS) and IPv6 (SRv6).

SPRING WG serves as a forum to discuss SPRING networks operations, define new applications of, and specify extensions of Segment Routing

technologies.



The forth bullet point is really interesting - because I have yet to see a last-call for this document on the mailing list - unless I missed it - which is explicitly required as per RFC2418 Section 3.2



I am not going to bother with the rest of the document - because well - people are free to their own technical opinions - but it greatly bothers me when the authors of a draft are publishing what are in effect blatant untruths in order to promote their work - and I believe it should bother everyone in this working group when such appears.



Thanks



Andrew

v2.23.0 | Report a Bug | By Email