Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"

Tom Herbert <tom@herbertland.com> Thu, 28 May 2020 18:32 UTC

Return-Path: <tom@herbertland.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 CBB823A0602 for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 11:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=herbertland-com.20150623.gappssmtp.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 T3N28V-C5KI5 for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 11:32:42 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 913893A053F for <ipv6@ietf.org>; Thu, 28 May 2020 11:32:42 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id g9so868853edr.8 for <ipv6@ietf.org>; Thu, 28 May 2020 11:32:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Xv/LeZXumOmlkFkGkURuboAudxa+so19K5F1UIVbdnw=; b=gL7gEIGzJIwuIsN63fOIgjqpzguQLjk3nnFfRHC+L4xCYXlVvwfvq4pLS3BaZEAjU0 H+S6yAwN94fWWC2ptSPL9BDyFVZEyPy/RZ5XqovFOguMfjhWRdJAplIZfzK5msfdRGrw e+TdnSzX2Q1Jv1w6wc+JfUuU/hk6XKkMTCf93KxvdcgwEpdldU+MLi8eAaPrAPBU+T3V dMUs2Aq5n4+i5GKag1hNQ1on1rGTKSwahMrDvltieLKXiQYniWTEWCELzq3MaqTp21/m aERqCvuoO5k/CN3lUv7u7eG51gP8K4qiCExLNo9zWWNsjqzko9symRuZxUvfAhOrDeY3 hUGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Xv/LeZXumOmlkFkGkURuboAudxa+so19K5F1UIVbdnw=; b=t4/uOLccj4SQ52x4jIf9HRz5HSvi8TjdR42mhRlwl+B9OGyNzVCPQmKgfVCLKRTZFt knlnteuicGfMCA5Ig+6QYakf7I14aZqbT/ZPFNuWUaaEhNAjVUtxR8rCqZ4X8uNm6HkT 8lzJtByP3acVIR6rGFgLSZxgQn1LhaUslipNVAyscm0fKGuQtlYXwbJ6ycAe4yhsB2eM EXFY9gNKTc8dkSUxfjzrVYVLy0F2m9Z6xIwcMz70+C25soHMtn02YxhKhmaBuDJSXPs8 /ZD766UGTg/ESvEVkchZ5WsnAu7l8gR7qiZHv1ytYkk6SxM2BafLDYygMm+c4dLItRry 1iJA==
X-Gm-Message-State: AOAM530bTD/wS70vAGjnd4sFv+11IAwZ7F9Dh5oVIOG4E1hacKivL7Z7 HTi9dyC9V5win+keJEz703MJMAb5BvrPFSNKJEqIoGO5
X-Google-Smtp-Source: ABdhPJxxKIXRDVYxth6doN8D1AHBuXbEZlcagNyUFAdE80eU6MSTmob5RKzhPF5/j4El6PNjtwrNcJFK5rsc/XScGsw=
X-Received: by 2002:a05:6402:2d4:: with SMTP id b20mr4629935edx.118.1590690760714; Thu, 28 May 2020 11:32:40 -0700 (PDT)
MIME-Version: 1.0
References: <19D30186-B180-4F65-BF00-7AD07CEF3925@gmail.com> <defcf5c6292345e7a333d600c4f47561@M10-HQ-ML02.hq.cnc.intra> <5eff7c35-f4f1-fa8f-2343-66896f3b42d9@joelhalpern.com>
In-Reply-To: <5eff7c35-f4f1-fa8f-2343-66896f3b42d9@joelhalpern.com>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 28 May 2020 11:32:28 -0700
Message-ID: <CALx6S34zxH2k=27uuGjOL8-bT5m2WTSBcxxHDmGAvejEsM6R9g@mail.gmail.com>
Subject: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: =?UTF-8?B?UmFuIFBhbmco6IGU6YCa6ZuG5Zui6IGU6YCa572R57uc5oqA5pyv56CU56m26Zmi5pys6YOoKQ==?= <pangran@chinaunicom.cn>, IPv6 List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bd92ec05a6b98d75"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PqEVaYN3KfJEnHMjFULIuk3aQ7w>
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: Thu, 28 May 2020 18:32:45 -0000

On Thu, May 28, 2020, 11:22 AM Joel M. Halpern <jmh@joelhalpern.com> wrote:

> Several people, including at least one I-D, have asserted that there is
> some abstract requirement for compatibility with SRvc6's SRH.  There is
> no such requirement.  That is not a criterion the 6man group needs to
> consider.  In my personal opinion, it is not even a constraint on what
> SPRING chooses to do.
>

Joel,

It's not even clear what compatibility with SRH means. The format of SRH is
very specific that SIDs are 128 bits, and the protocol has no sufficient
extensibility mechanism that allows that to change without breaking
backwards compatibility. As far as I can tell, changing or compressing SIDs
requires a new routing type regardless of the compression method or who
specifies it.

Tom


> Yours,
> Joel
>
> On 5/28/2020 3:38 AM, Ran Pang(联通集团联通网络技术研究院本部) wrote:
> > Hi WG,
> >
> > It seems like CRH is not compatible with SRv6 and SRH. We need to
> > discuss how CRH cooperates with uSID, G-SRv6 or other SRv6 header
> > compression solutions before adoption, or whether CRH will cause
> > difficulties in the deployment of G-SRv6 and other solutions. At
> > present, we tend to choose solutions compatible with SRH.
> >
> >
> > Thanks,
> >
> > Ran
> >
> >
> >     *From:* Bob Hinden <mailto:bob.hinden@gmail.com>
> >     *Date:* 2020-05-16 06:13
> >     *To:* IPv6 List <mailto:ipv6@ietf.org>
> >     *CC:* Bob Hinden <mailto:bob.hinden@gmail.com>
> >     *Subject:* Adoption Call for "The IPv6 Compact Routing Header (CRH)"
> >     This message starts a two-week 6MAN call on adopting:
> >     Title:          The IPv6 Compact Routing Header (CRH)
> >     Authors:        R. Bonica, Y. Kamite, T. Niwa, A. Alston, L. Jalil
> >     File Name:      draft-bonica-6man-comp-rtg-hdr-21
> >     Document date:  2020-05-14
> >     https://tools.ietf.org/html/draft-bonica-6man-comp-rtg-hdr
> >     as a working group item. Substantive comments regarding adopting
> >     this document should be directed to the mailing list.  Editorial
> >     suggestions can be sent to the authors.
> >     Please note that this is an adoption call, it is not a w.g. last
> >     call for advancement, adoption means that it will become a w.g.
> >     draft.  As the working group document, the w.g. will decide how the
> >     document should change going forward.
> >     This adoption call will end on 29 May 2020.
> >     The chairs note there has been a lot of discussions on the list
> >     about this draft.   After discussing with our area directors, we
> >     think it is appropriate to start a working group adoption call.  The
> >     authors have been active in resolving issues raised on the list.
> >     Could those who are willing to work on this document, either as
> >     contributors, authors or reviewers please notify the list.   That
> >     gives us an indication of the energy level in the working group
> >     to work on this.
> >     Regards,
> >     Bob and Ole
> >
> > 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-
> > spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送
> > 目录中删除。 If you have received this email in error please notify us
> > immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn ,you can
> > unsubscribe from this mail. We will immediately remove your information
> > from send catalogue of our.
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>