Re: [spring] Conclusion of Adoption call for draft-filsfilscheng-spring-srv6-srh-compression
Robert Raszuk <robert@raszuk.net> Sun, 31 October 2021 19:04 UTC
Return-Path: <robert@raszuk.net>
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 EA3153A11ED for <spring@ietfa.amsl.com>; Sun, 31 Oct 2021 12:04:22 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 ZNSm2JMuQpPS for <spring@ietfa.amsl.com>; Sun, 31 Oct 2021 12:04:18 -0700 (PDT)
Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06DDF3A11EC for <spring@ietf.org>; Sun, 31 Oct 2021 12:04:17 -0700 (PDT)
Received: by mail-ua1-x930.google.com with SMTP id o26so28127597uab.5 for <spring@ietf.org>; Sun, 31 Oct 2021 12:04:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WaG9oEO33UE0H4BVJRHmQri030ogpA3rBatS+PL5n44=; b=fN141MEY2IcTSW3ZEgCuMYnN1M43M3ewwDunjHxjTP/qNsl5t/yNRkf8SRWl0haqoc pd+xvFIJUrLHAE8xcm9/ApV1+o0eVglfYWceUMpjwEpkBnpa8FHeVvQUVhz+Zq6jBvmp tOGPQr8jgrdnVsAHg8mwm7SsCO7oHfh/d4QRAEVk8X+4d0Y4JY0t2Lyg/Q+iLMBDp9eM FZaA4U7BilADcqKsFgVYMB8R9QBs9e7jsDk4cfXZMtH0k780GYzYnBdphwf0wHZ8gIFX JxUeQvlt8UFNUossbG4MMIt5Eln82ycxz18t3US+IR1DPcasGRhkimLq0mst+/+4P65f NgZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WaG9oEO33UE0H4BVJRHmQri030ogpA3rBatS+PL5n44=; b=zdsDpaOfr7dYu8OpR3PxB+xOsFT5w/mGEYLlVGGfBM9V7MwHoNY2Yi7ocyWpgSyrhE 1x/eCTGXRBvQ72N4Sx70VWSAVdBCMu+ofDXyTFk3JY9aaKaTlC+piO86mwl4htpgPQR1 epu4bmcwrDaIsKHGjB4vwJD0VdP3JIv32WlgLSP2gQt/q1tuLH/tp0xIKyix+XH1bXbt cg6hZIxn5KfATvpXNnuyHTmNHBaTAMseYeS0BL30AuwejhS9xhtA6PGRSlO5yhtO4S8n oLbNOnor7BSiOLvrjKBqeG86gEJHd3y/fAfX+SN+FNtXdmPWi1RMlxsLee5IeYpv23yQ i/pA==
X-Gm-Message-State: AOAM531i4Dk80h1UEtvcDkra0dQ1EKTqqMHL3V5Ec4v1wl/FAO3HQ9yg 2TBTVBH0eT2mquoyzgQt8CFGdIDiu+RyueATHkLgyhxWk7Q=
X-Google-Smtp-Source: ABdhPJz2ZnS15uajE96pu+QVqGKyy9pegBgMEY+BcyDi+Lu7a/u6csQqzuvzMKM26leJyzf30wvVizV7YHAxfacJk3o=
X-Received: by 2002:a05:6102:34ec:: with SMTP id bi12mr3346856vsb.0.1635707056642; Sun, 31 Oct 2021 12:04:16 -0700 (PDT)
MIME-Version: 1.0
References: <7bab18c1-7f45-3e8f-791e-2d3020303631@joelhalpern.com> <CAOj+MMF90kp-W9GVgy4Nb1sQpK31pT3LUURTe9_HYU=_nPxs0A@mail.gmail.com> <db597f79-bbd1-be4a-d409-1e5349e9ad5d@joelhalpern.com> <CAOj+MMGkfJCn+rXPCU80hhbt+V-gJKbVuJP_-muaiU4LQZ+uxA@mail.gmail.com> <de50077f-1e5b-4a07-cdbd-ca4a6d1ef644@joelhalpern.com>
In-Reply-To: <de50077f-1e5b-4a07-cdbd-ca4a6d1ef644@joelhalpern.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Sun, 31 Oct 2021 20:04:19 +0100
Message-ID: <CAOj+MMEqH7W-Kndzj8vyutDRabn+3m+J5z5=hZAjrnyexyeaFg@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000011700105cfaabaaf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/_ysqzqJl8aiXD7M3MNR7hp9z5bY>
Subject: Re: [spring] Conclusion of Adoption call for draft-filsfilscheng-spring-srv6-srh-compression
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: Sun, 31 Oct 2021 19:04:23 -0000
Yes, the discussions in both SPRING and 6man prove that there is a group of folks who either do not like and do not accept the existence of RFC 8986 or simply do not fully understand what it contains. I do not think that as such it is sufficient not to accept the document as a WG draft observing the amount of industry support for it as expressed on the list. At min as requested a solid list of technical issues should have been provided where text in the draft goes above to what is already written in RFC8986. Kind regards, Robert. On Sun, Oct 31, 2021 at 7:47 PM Joel M. Halpern <jmh@joelhalpern.com> wrote: > From my perspective the discussions as part of the adoption call in > SPRING, and the discussions in 6man make it clear that there is an issue > to be resolved. It may be that the issue will be resolved in saying > there is nothing that needs to be specified. It may be resolved by > saying that there are differences, and that they are acceptable. There > are many other ways that it may be resolved. > > It is my job as chair, given the policy, to determine that there is an > apparent discrepancy that needs to be addressed. I have done so. > > Yours, > Joel > > On 10/31/2021 2:31 PM, Robert Raszuk wrote: > > > > I am not attempting to revisit the question of whether RFC 8986 > > complies > > with RFC 4191. > > This compression documents raises additional issues beyond those in > > 8986 > > in some aspects of the flavors it describes. > > > > > > Could you be so kind and enumerate where in the draft you see *anything* > > crossing the line by defining new semantics for the ARG part of the SID > > as defined in RFC8986 ? > > > > Hint: your argument could have been sustainable if RFC8986 would put > > additional restrictions on the ARG field. But it does not. > > > > Many thx, > > Robert > > >
- [spring] Conclusion of Adoption call for draft-fi… Joel M. Halpern
- Re: [spring] Conclusion of Adoption call for draf… Robert Raszuk
- Re: [spring] Conclusion of Adoption call for draf… Joel M. Halpern
- Re: [spring] Conclusion of Adoption call for draf… Robert Raszuk
- Re: [spring] Conclusion of Adoption call for draf… Joel M. Halpern
- Re: [spring] Conclusion of Adoption call for draf… Robert Raszuk
- Re: [spring] Conclusion of Adoption call for draf… Joel M. Halpern
- Re: [spring] Conclusion of Adoption call for draf… Darren Dukes (ddukes)
- Re: [spring] Conclusion of Adoption call for draf… Joel M. Halpern
- Re: [spring] Conclusion of Adoption call for draf… Robert Raszuk
- Re: [spring] Conclusion of Adoption call for draf… Joel M. Halpern
- Re: [spring] Conclusion of Adoption call for draf… Robert Raszuk
- Re: [spring] Conclusion of Adoption call for draf… Joel Halpern Direct
- Re: [spring] Conclusion of Adoption call for draf… Darren Dukes (ddukes)
- Re: [spring] Conclusion of Adoption call for draf… Joel M. Halpern