Re: [spring] WGLC for draft-ietf-spring-segment-routing-policy

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 30 April 2021 16:57 UTC

Return-Path: <jmh@joelhalpern.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 EAB583A1F71; Fri, 30 Apr 2021 09:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 wepgwHrsE_WC; Fri, 30 Apr 2021 09:57:13 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 10BFD3A1F73; Fri, 30 Apr 2021 09:57:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4FWz7D5MR7z6GB40; Fri, 30 Apr 2021 09:57:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1619801832; bh=qbf9OefKZQioTlPn4LXtyf6TKOQY97Yhvhxik8vL2C4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=ivSlnRESP102kr6XZjsP8ZetTDd+viF1hL8sa4XjwoSyU097LdHWG0hWT6RDc5n7K /Zt/1sxvcgPgoqScgAzFZnzQU1yiNkoI0NPlcXx1w414fgCUxzK/bazE+yYh97MQVJ +14bPS+vnQu7/wKHF+7nYDsQiWGdhZxsZY32KR1I=
X-Quarantine-ID: <x80aexAPR9Ma>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4FWz7C5ybxz6GB04; Fri, 30 Apr 2021 09:57:11 -0700 (PDT)
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Boris Hassanov <bhassanov=40yahoo.com@dmarc.ietf.org>, "spring@ietf.org" <spring@ietf.org>, James Guichard <james.n.guichard@futurewei.com>
Cc: "spring-chairs@ietf.org" <spring-chairs@ietf.org>
References: <MN2PR13MB4206EF1F6E9B1C01BDDCDD76D24D9@MN2PR13MB4206.namprd13.prod.outlook.com> <256008865.754508.1619557990591@mail.yahoo.com> <MW3PR11MB457051E36837BB99BAB05C18C1409@MW3PR11MB4570.namprd11.prod.outlook.com> <210578080.1206207.1619795931098@mail.yahoo.com> <MW3PR11MB457044275F37FD9E1145B143C15E9@MW3PR11MB4570.namprd11.prod.outlook.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <64bade9d-f3ba-6434-9a78-d59790273a3b@joelhalpern.com>
Date: Fri, 30 Apr 2021 12:57:11 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <MW3PR11MB457044275F37FD9E1145B143C15E9@MW3PR11MB4570.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/yAWUCXMhZ3plYfAsSJqw_js03tU>
Subject: Re: [spring] WGLC for draft-ietf-spring-segment-routing-policy
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, 30 Apr 2021 16:57:18 -0000

It would seem very strange to add an implementation section at WGLC, 
since by IETF policy they are removed before RFC publication.  (For 
context, the driving reason for removal is that they inherently become 
obsolete.)

It is reasonable to include comments on implementation in the shepherd 
writeup.  That has to be short.  Authors, can you clarify whether it 
would be accurate for Jim to report "there have been implementations for 
many years, and multiple interoperability tests" ?

Thank you,
Joel

On 4/30/2021 12:12 PM, Ketan Talaulikar (ketant) wrote:
> Hi Boris,
> 
> I will leave it the chair/shepherd guidance on this one.
> 
> EANTC has been running multi-vendor interop for Segment Routing that 
> covers this document along with signalling protocols like PCEP and 
> BGP-SRTE every year since at least 2016. It includes various controller 
> and router products. Their results are published in whitepapers which 
> might perhaps provide at least some of the information that you are looking.
> 
> Thanks,
> 
> Ketan
> 
> *From:*Boris Hassanov <bhassanov=40yahoo.com@dmarc.ietf.org>
> *Sent:* 30 April 2021 20:49
> *To:* spring@ietf.org; James Guichard <james.n.guichard@futurewei.com>om>; 
> Ketan Talaulikar (ketant) <ketant@cisco.com>
> *Cc:* spring-chairs@ietf.org
> *Subject:* Re: [spring] WGLC for draft-ietf-spring-segment-routing-policy
> 
> Hi Ketan,
> 
> Yes, I meant an implementation status section in the draft.
> 
> The either one way, which will be easier to accomplish. We need to fix 
> such status somewhere, IMO.
> 
> Thank you.
> 
> SY,
> 
> Boris
> 
> On Wednesday, April 28, 2021, 8:48:06 AM GMT+3, Ketan Talaulikar 
> (ketant) <ketant=40cisco.com@dmarc.ietf.org 
> <mailto:ketant=40cisco.com@dmarc.ietf.org>> wrote:
> 
> Hi Boris,
> 
> Thanks for your review and feedback.
> 
> Did you imply that we add an add an implementation status section in the 
> draft?  Or are you suggesting that the chairs poll for implementation 
> and deployment status? I ask because the Implementation Status section 
> is generally removed before publication as RFC.
> 
> Regarding implementation, I am aware of support for this draft in 
> Cisco’s Routing products for many years now with multiple deployments. I 
> am also aware of other vendor support & operator deployment. However, 
> would request other WG members to respond/confirm.
> 
> Thanks,
> 
> Ketan
> 
> *From:*spring <spring-bounces@ietf.org <mailto:spring-bounces@ietf.org>> 
> *On Behalf Of *Boris Hassanov
> *Sent:* 28 April 2021 02:43
> *To:* spring@ietf.org <mailto:spring@ietf.org>; James Guichard 
> <james.n.guichard@futurewei.com <mailto:james.n.guichard@futurewei.com>>
> *Cc:* spring-chairs@ietf.org <mailto:spring-chairs@ietf.org>
> *Subject:* Re: [spring] WGLC for draft-ietf-spring-segment-routing-policy
> 
> Hi James and all,
> 
> I read the draft and strongly support its publication as WG document. 
> Very detailed, helpful and interesting document.
> 
> I would only add implementation status part because currently it is not 
> easy to get such info about implementation details.
> 
> Thank you.
> 
> SY,
> 
> Boris
> 
> On Thursday, April 15, 2021, 9:57:11 PM GMT+3, James Guichard 
> <james.n.guichard@futurewei.com <mailto:james.n.guichard@futurewei.com>> 
> wrote:
> 
> Dear WG:
> 
> This email starts a 2 week Working Group Last Call for 
> draft-ietf-spring-segment-routing-policy [1].
> 
> Please read this document if you haven’t read the most recent version 
> and send your comments to the SPRING WG list no later than April 29^th 
> 2021.
> 
> If you are raising a point which you expect will be specifically debated 
> on the mailing list, consider using a specific email/thread for this point.
> 
> Lastly, if you are an author or contributors for this document please 
> response to the IPR call in the previous email thread.
> 
> Thanks!
> 
> Jim, Joel & Bruno
> 
> [1] 
> https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-policy/ 
> <https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-policy/>
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org <mailto:spring@ietf.org>
> https://www.ietf.org/mailman/listinfo/spring 
> <https://www.ietf.org/mailman/listinfo/spring>
>