Re: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming

"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com> Thu, 27 February 2020 21:13 UTC

Return-Path: <pcamaril@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 176A23A0C13; Thu, 27 Feb 2020 13:13:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=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=f+Ugot9T; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=gkIEK03z
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 ricNWC2aWjGF; Thu, 27 Feb 2020 13:13:53 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E6893A0C16; Thu, 27 Feb 2020 13:13:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3528; q=dns/txt; s=iport; t=1582838033; x=1584047633; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=GTS8xDKodHXazHAAxqP9Dk4j55ZkKORjbyY6n5zv9FM=; b=f+Ugot9TSxl/Y9pSYBS5v3//sLvJbXqEGZr+BXFWzeb/66Mm5TWSf13n 7T8L+e72W/en4ass27YcLGAXmN0o75Z44WFGcxWHIS0ilO2TxUh8+2+cW fd1ySUpaa4t3XDGkRmBClP0v5yRyHfmR81D8yUMWcmpRjtzLBL6l01znh 4=;
IronPort-PHdr: 9a23:iNM9ARWNodG7M3CKyIVVstLUTETV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtankiF81HXUVk+1mwMFNeH4D1YFiB6nA=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DWBQCUMFhe/4UNJK1mHAEBAQEBBwEBEQEEBAEBgXuBVFAFbFggBAsqCoQKg0YDimeCX4ljjjGBQoEQA1QJAQEBDAEBJQgCBAEBhEACF4FxJDgTAgMNAQEFAQEBAgEFBG2FNwyFYwEBAQECARIREQwBATcBBAcEAgEIEQMBAgMCHwcCAgIfERUICAEBBA4FIoMEAYJKAw4gAQMLpHwCgTmIYnWBMoJ/AQEFgS8Bg2ANC4IMAwaBDiqMJRqBQT+BEScggh4uPmsZAYEWSQKBSxqDETKCLJBlj0+OcDJECoI8h1GKXoQ2HIJJiBuHAYlJRJcogi6QHQIEAgQFAg4BAQWBaSKBWHAVGiEqAYINAQEyUBgNjh0YIIM7hRSFQXQCgSeMegGBDwEB
X-IronPort-AV: E=Sophos;i="5.70,493,1574121600"; d="scan'208";a="731025210"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Feb 2020 21:13:51 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 01RLDpXQ009556 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 27 Feb 2020 21:13:51 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 27 Feb 2020 15:13:50 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 27 Feb 2020 15:13:50 -0600
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 27 Feb 2020 15:13:50 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=D1I/nRNnaovNMsJQ5Q3a1G3suJTH9MJVUSMnH2S0De+oNOWI//olIXDJOANeQ9mTySRf1wtRwjRUvp02y7e7Bq8rOJX/BSa0fUsIiX8M86iNaFNgHMCP1azgSrylEtPVGFqyLfd8HltFl6nN6JbQYPRROVB/oGTWFCzx3L9OdTCNeP6zwOkZGXwObdYNs1KK1+kqcY7B+AyJspEpegnOHzWWlER4i66VsqaO+gXJJpFS4dGZG3h70aMehj9P1USYkdf7oWkEbWQYnmkSqWn1hCFmtSHikn7YsulV7N/WOD8oyyEQVU/FQNQliLEE7AtpHxRqsXn3UarzFFUk3Zxsuw==
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=GTS8xDKodHXazHAAxqP9Dk4j55ZkKORjbyY6n5zv9FM=; b=d96xkhTjgyxaNah8hgK0YtVOteDxVwmTjhCLIZW1C+zX+nnrYoUBJVCjExIrXQgyzne3d7jq9C8aaZ32f6CJsT+D2l14fzWGbZ+7o3Za+LmIrfx6lQ26xYt73Hasy4CF4ZFZq6BqzAhsK3wBfOvtIvkXLByP2jKO1orY/GHTahQzd/XZ6JanrEwRKrv9fjaIdQONPPZVFju35LFQC8TyUHM93+6R2guWE37MwGO1NFSA/Jpwt3Oa/kxLXK+5rlToCjF6UrQScrkdjXkvCB2eN6jJW9G7CXsZ1dgdJG38EoJEoxEl02vAoy1ihV4aAhV4v840oH35NVyAJDV18Mz/jA==
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=GTS8xDKodHXazHAAxqP9Dk4j55ZkKORjbyY6n5zv9FM=; b=gkIEK03z1jnowhB1ziyULk7h/RKuN8Kai/PnVrhVmo+VgyHnpa5GLNmQV+BenVXl7U+JXRW5b3nVB+dFoIYvV/cu1I9QWlcrzHLCBmrEOVEk5PZPF8qRFGyVxWcsCovXKbub4KezJ8pnk4PPC6kF+cOP1oDshFt7lS9YM8ZYp74=
Received: from MWHPR11MB1374.namprd11.prod.outlook.com (10.169.234.8) by MWHPR11MB1951.namprd11.prod.outlook.com (10.175.52.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.17; Thu, 27 Feb 2020 21:13:46 +0000
Received: from MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::e481:a191:e31:f948]) by MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::e481:a191:e31:f948%12]) with mapi id 15.20.2772.012; Thu, 27 Feb 2020 21:13:46 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Lizhenbin <lizhenbin@huawei.com>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Thread-Topic: Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
Thread-Index: AdXsmBuY1tqntXEdSECRXFRXLBEUfQATzO+AADO8wIA=
Date: Thu, 27 Feb 2020 20:38:41 +0000
Message-ID: <67ECB7F5-86E5-4AE9-B8EB-B06203978B35@cisco.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D9364A1C2@DGGEMM532-MBX.china.huawei.com> <a93c23e5-eb65-f84a-6289-6f1221c68f2d@gmail.com>
In-Reply-To: <a93c23e5-eb65-f84a-6289-6f1221c68f2d@gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.22.0.200209
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pcamaril@cisco.com;
x-originating-ip: [213.4.210.210]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 04b32cec-b2a7-42cd-776e-08d7bbc9eea6
x-ms-traffictypediagnostic: MWHPR11MB1951:
x-microsoft-antispam-prvs: <MWHPR11MB1951BB4908388F7D9355BD32C9EB0@MWHPR11MB1951.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 03264AEA72
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(136003)(396003)(366004)(39860400002)(189003)(199004)(64756008)(66556008)(478600001)(91956017)(76116006)(66476007)(6666004)(66946007)(4326008)(6486002)(66446008)(8936002)(186003)(26005)(8676002)(81166006)(54906003)(33656002)(6512007)(86362001)(53546011)(5660300002)(36756003)(6506007)(316002)(2616005)(81156014)(966005)(6916009)(2906002)(71200400001); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1951; H:MWHPR11MB1374.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: ouvOwy1Olyal4+/j90IBfX3o7wIrKBFrQmyMx4GOogRnVrqdbG4qph0YxdB5bpCP2sOmJyHTZblhJ8PpZMX3ldTct/2QeeZFuih7tSP5ZM1Bei49T3+ErZLCphtFIe4g/WTVzsDx463V2dLBqkF4fK3LviiANuhjY+0Wiy/X+1bSLdmL3O0UyWcylZFaIrIoHMp/Vh0G/EW0iZXK6q7nu5rrK+8Wu9gMDVkjZpFdyD9ZIgLhqNGQdmsi1VbxWeZCM5TFf28JETwvKqZivQO9rPSTMWdl1OaXYJMfE+yyTMFYtG6P2qogcWcXTIIH6ZzhOuKPb9UnIx8/B4d6mhpnHmgJxQVMV+rVClxBN0ZKRJCf6x2OhGGEi7M/uqmZsJpv8VjekQ08d4kesU0rpx3CvWOvSzuye5Avr/o6UdpEW1+NVp4gFsWDZi59V4/Ou41+enTu/hSDrGydY1yZ7mDoFK2CetpKo+deXFWgnr3tM070HdsC6/6/r+9Coe1QhwAVA0SpEBogSIB2pZzJg7dd4A==
x-ms-exchange-antispam-messagedata: i/S+xh+yu51R8x/QCIg4ydDVK8IG6C0pO/dHzMMhR+FKMTO551SHQqwyEDF0d3xSM0nwvPpE9494UhxUsIsLHKMHQ05OpLXvuyiS+tULyClQMpgvC2cUMM1czFwqBgp2juDwQ7d8GBsTZcCfakQAaw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <6D85EA7C16974A44800C1C5D8F90208A@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 04b32cec-b2a7-42cd-776e-08d7bbc9eea6
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2020 21:13:46.1002 (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: gbIV5hwizthoxP+laRPh+IBDSumFt3T8gvNGa1y/1SRzVrQ5cQg/CPiaRm++c6P+U7fWdZPGM44Mvp4pjjF23w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1951
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/lf7tzEm7qx5Ik_dDlGCkYaH01z4>
Subject: Re: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
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: Thu, 27 Feb 2020 21:13:55 -0000

 Brian,

>     For example, the word "pop" is used but still not defined. In computer science, it generally refers to popping a stack. I understand that in the MPLS context (a label stack) but not in the IPv6 context, where there is no stack in the header.

You raised such comment on December 7th 2020 at the mailer with respect to draft-ietf-spring-srv6-network-programming-05.
We iterated throughout December publishing the clarifications that you requested in rev06 and 07.
https://mailarchive.ietf.org/arch/msg/spring/Y7XKvgshM8ces-HbkT2uQa37a_w/
https://mailarchive.ietf.org/arch/msg/spring/VpLfcUvDXHzMOU6fTE1_XPzhd68/
https://mailarchive.ietf.org/arch/msg/spring/mXcsWXaISqjzs7g_fJZYhcKabgY/

Also, the word pop is still used in the section title, but it has been removed from the definition of the behavior.

Could you please see the latest version of the draft?

Thanks,
Pablo.

-----Original Message-----
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wednesday, 26 February 2020 at 21:57
To: Lizhenbin <lizhenbin@huawei.com>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>, 'SPRING WG List' <spring@ietf.org>
Cc: "6man@ietf.org" <6man@ietf.org>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
Resent from: <alias-bounces@ietf.org>
Resent to: <cf@cisco.com>, <pcamaril@cisco.com>, <john@leddy.net>, <daniel.voyer@bell.ca>, <satoru.matsushima@g.softbank.co.jp>, <lizhenbin@huawei.com>
Resent date: Wednesday, 26 February 2020 at 21:57

    >  In the process all the comments have been resolved 
    
    Unfortunately, this is not true.
    
    For example, the word "pop" is used but still not defined. In computer science, it generally refers to popping a stack. I understand that in the MPLS context (a label stack) but not in the IPv6 context, where there is no stack in the header.
    
    The text explaining penultimate segment pop, quite apart from using "pop" in this undefined way, still does not explain how it is compatible with the RFC8200 interdiction of inserting or removing headers en route. It explicitly describes removing a header before the final routing hop, which is explicitly against RFC8200.
    
    As far as I'm concerned, these comments have been brushed aside.
    
    The fact that there's running code is good, but it doesn't resolve anything in the text.
    
    Regards
       Brian Carpenter