Re: 6man w.g. last call for <draft-ietf-6man-spring-srv6-oam>

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 04 December 2019 21:37 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4A21200A3; Wed, 4 Dec 2019 13:37:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.635
X-Spam-Level:
X-Spam-Status: No, score=0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 ESg4eNo35TId; Wed, 4 Dec 2019 13:37:20 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 18CD412004C; Wed, 4 Dec 2019 13:37:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 47SsdD05JWz1ntF1; Wed, 4 Dec 2019 13:37:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1575495440; bh=e/JQEIEaoxgfWSkgKNFTMKgbv7YxvZ0llfx9bXeph/s=; h=Subject:To:References:From:Date:In-Reply-To:From; b=WQry76ErNsDshk+9pksyfc+KLUWrzsmwjRFLQYEv3n0B8KbYIwqHtl46z4zB2jz2E Io10OhT8Cd9hJe0VrL1abkTcRNvJm1OCyA49Zx8qXPwJLkL/xkzCrnp35CETRSu1oP 2pcoO6vYU8biPcJZNLRJULwNCZ88Bz4ju27WFJxc=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.20.3.198] (unknown [45.225.71.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 47SsdB48MCz1ntDx; Wed, 4 Dec 2019 13:37:18 -0800 (PST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-spring-srv6-oam>
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>, SPRING WG <spring@ietf.org>
References: <ECC21DA8-0156-41D2-921E-177389D3C904@employees.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <15bc440b-1dbc-0930-137f-f016ca527c2c@joelhalpern.com>
Date: Wed, 04 Dec 2019 16:37:15 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <ECC21DA8-0156-41D2-921E-177389D3C904@employees.org>
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/ipv6/3CdVcU6v8NrcmFblHmowOnlSYhM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2019 21:37:21 -0000

I re-read this draft, and I am afraid it is currently under-specified.

In order for the various examples to work, there is assumed behavior by 
the processor to which packets are punted.  I could not find where this 
normative behavior is described explicitly.  It appears that the 
behavior requires that the node "punt processor" look past the SRH and 
make determinations based on the content.  This needs to be described 
explicitly.  And it needs some discussion of why it is legitimate to 
look past the SRH when the SRH does not show SL=0.

Yours,
Joel

On 12/4/2019 3:53 PM, Ole Troan wrote:
> Hello,
> 
>    As agreed in the working group session in Singapore, this message starts a new two week 6MAN Working Group Last Call on advancing:
> 
>    Title    : Operations, Administration, and Maintenance (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6)
>    Author   : Z. Ali, C. Filsfils, S. Matsushima, D. Voyer, M. Chen
>    Filename : draft-ietf-6man-spring-srv6-oam-02
>    Pages    : 23
>    Date     : 2019-11-20
>                           
>      https://datatracker.ietf.org/doc/draft-ietf-6man-spring-srv6-oam/
> 
> as a Proposed Standard.
> 
> Substantive comments and statements of support for publishing this document should be directed to the mailing list.
> Editorial suggestions can be sent to the author. This last call will end on the 18th of December 2019.
> 
> To improve document quality and ensure that bugs are caught as early as possible, we would require at least
> two reviewers to do a complete review of the document.  Please let the chairs know if you are willing to be a reviewer.
> 
> The last call will be forwarded to the spring working group, with discussion directed to the ipv6 list.
> 
> Thanks,
> Bob & Ole, 6man co-chairs
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>