Re: [spring] Status of draft-ietf-spring-srv6-network-programming?

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 11 March 2020 18:32 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 904AA3A10F9 for <spring@ietfa.amsl.com>; Wed, 11 Mar 2020 11:32:52 -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, 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 OBV68wq8iEKQ for <spring@ietfa.amsl.com>; Wed, 11 Mar 2020 11:32:50 -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 789C83A10F2 for <spring@ietf.org>; Wed, 11 Mar 2020 11:32:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 48d0v62gJrz6GD6d; Wed, 11 Mar 2020 11:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1583951570; bh=qHqEL7Q0drHrPXWc9Zub7+1KowrW7pNkkaNn4qYY9kk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Sb5zJKiWSj404oKpCWOqpcNHiemPZU2ZTtOo0HhWeBWqk1jv9TbUIdTsKIpm+0Lph I+cGMI2UbORuSO6LQwJDbrReKOpJzs9AzngSKTbdz2s/47IwZagluprSxcwRSf1eaJ LhKh32SFg1h2oeN8lFnHnu2M+WtZtM47tEL44Sg0=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 48d0v5693Zz6GD1w; Wed, 11 Mar 2020 11:32:49 -0700 (PDT)
To: bruno.decraene@orange.com
Cc: "spring@ietf.org" <spring@ietf.org>
References: <9be305c6-feca-9ff7-60cd-32f3b4fee123@gont.com.ar> <8ec5f424-4d15-6e23-c26f-d51c13506c0b@gont.com.ar> =?utf-8?q?=3C26051=5F158?= =?utf-8?q?3950351=5F5E692A0F=5F26051=5F192=5F1=5F53C29892C857584299CBF5D053?= =?utf-8?q?46208A48DE621C=40OPEXCAUBM43=2Ecorporate=2Eadroot=2Einfra=2Eftgro?= =?utf-8?q?up=3E?=
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <76dffa38-f320-63bb-d740-501fb8b94e02@joelhalpern.com>
Date: Wed, 11 Mar 2020 14:32:49 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: =?utf-8?q?=3C26051=5F1583950351=5F5E692A0F=5F26051=5F192=5F1=5F?= =?utf-8?q?53C29892C857584299CBF5D05346208A48DE621C=40OPEXCAUBM43=2Ecorporat?= =?utf-8?q?e=2Eadroot=2Einfra=2Eftgroup=3E?=
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/EuJwUeIyyXonE0aGHCqwT2fd5G8>
Subject: Re: [spring] Status of 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: Wed, 11 Mar 2020 18:32:53 -0000

Bruno, I can not speak for anyone else.  But I have made clear to the 
authors (on list) and the AD (off list) that the current revision of the 
document does not provide what I consider adequate explanation of the 
consequence of the PSP issues.

If progress is such an important concern, then put out NP without PSP, 
and issue a separate document with PSP.  The NP document (quite 
correctly) does not claim to be a complete compilation of all behaviors 
or all flavors.

 From other people's questions about the PSP processing, it seems that 
the text is still not clear about what SID has the PSP flavor (I think I 
know how that is supposed to work, but the degree of accidental 
misinterpretation suggests the document could be better.)

Yours,
Joel

On 3/11/2020 2:12 PM, bruno.decraene@orange.com wrote:
> Fernando,
> 
>> From: Fernando Gont [mailto:fernando@gont.com.ar]
>> Sent: Wednesday, March 11, 2020 5:06 AM
>>
>> Folks,
>>
>> Ping?
>>
>>
>> On 6/3/20 06:25, Fernando Gont wrote:
>>> Marting & Bruno,
>>>
>>> May I ask what's the status of this I-D?  -
>>>
>>> On one hand, both of you declared consensus to move it forward. On
>>> another hand, the authors keep making changes to address comments (good)
>>> so what the wg will ship will be different from what the document on
>>> which you claimed consensus. Besides, the datatracker lists the document
>>> as "in WGLC".
>>>
>>> So:
>>> What's the status of this document?
>>> And.. are you planning to do a second WGLC?
>>>
>>>
> 
> The call for comments is closed and I believe people had ample time to review the document and make comments.
> Till then, authors have been working on addressing the received comments, and updating the document.
> Some occasional new questions or points are been raised, but I don't see anything wrong with this. This may happen after the WGLC (e.g. during AD review, during IETF last call, during IESG review, and when the RFC is published via email or errata).
> I'm in the process of writing the shepherd write up.
> 
> Reviewing all the diff on all versions of the document, I don't see large technical changes that would require a formal review of those changes though a second WG last call.  Except one change regarding the processing of the upper layer, that has recently been raised by Chris. Let's see the solution on this.
> Other than that, the changes are:
> - some editorial clarifications
> - removal of OAM references & counters (Greg's comment)
> - large editorial changes in the PSP section to provide more clarification and context and explicit the consequences. But with no change to the technical behavior.
> 
> Do you see a need for a formal review of some changes?
> 
> Thanks,
> --Bruno
> 
>>> Thanks,
>>
>>
>> -- 
>> Fernando Gont
>> e-mail: fernando@gont.com.ar || fgont@si6networks.com
>> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>>
>>
>>
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>