[spring] regarding the replication segment draft

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 08 July 2020 16:07 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 72DE83A0EFF for <spring@ietfa.amsl.com>; Wed, 8 Jul 2020 09:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 n5OyjwR9KOiv for <spring@ietfa.amsl.com>; Wed, 8 Jul 2020 09:07:08 -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 977203A0EF8 for <spring@ietf.org>; Wed, 8 Jul 2020 09:07:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4B24243jnCz6G7Zc for <spring@ietf.org>; Wed, 8 Jul 2020 09:07:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1594224428; bh=1EehXpCTt4gr/kuVIs0/0m+jvmsxVfh+qBbwy8/lR2s=; h=To:From:Subject:Date:From; b=Zefy9ZkBiyvCRMF0gCnR2sv14UO7QJ2LJo17VGIVH+NWQ82A9hycCW77ZJEv1Mxr7 zYKgkzAKOH8eji5njafzh+4++a6APu+1UN6ivJL4AaZfgCwHxCGoreFL8QqNuMrPae 3XMpNDURNQloKV/SuUhE0YmQ3lylligmu1moUchY=
X-Quarantine-ID: <8lpf05rMHyk6>
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 4B24240jKkz6GD4H for <spring@ietf.org>; Wed, 8 Jul 2020 09:07:08 -0700 (PDT)
To: "spring@ietf.org" <spring@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <298cdda3-427e-deaf-a656-010f8e46471d@joelhalpern.com>
Date: Wed, 8 Jul 2020 12:07:06 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
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/Q466mOx_d6383lNRiHwNRdFW85U>
Subject: [spring] regarding the replication segment draft
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, 08 Jul 2020 16:07:10 -0000

I am told that I was unclear in some aspects of my comments.

Speaking as an individual:
1) I hope and expect we can get to adopting this.  I have no objection 
to the idea
2) As I see it, before we can adopt this draft we need enough 
description of the operational requirements / restrictions (e.g. where 
can replication segments appear, how are replication trees described, 
where can conventional SIDs appear in a stack with replications segments?)
2') Note that the descriptions do not have to be perfect.  I do 
understand that we are at WG adoption, not WG last call.
3) Just for completeness, I understand that the control aspects are out 
of scope, and are being dealt with in other working groups (presumably 
with  appropriate cross-communication)

Yours,
Joel