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

Greg Mirsky <gregimirsky@gmail.com> Thu, 28 May 2020 19:54 UTC

Return-Path: <gregimirsky@gmail.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 F406D3A0B0C for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 12:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 kGT0fgnpfrlP for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 12:54:52 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 D2EAF3A0B06 for <ipv6@ietf.org>; Thu, 28 May 2020 12:54:51 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id x22so17305201lfd.4 for <ipv6@ietf.org>; Thu, 28 May 2020 12:54:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZbVHN6Ai7oSvkmk6pxZAW2SXDkr5YkqpAYbFFOcrcjQ=; b=W9trA4/cTPPzuD5bQXWzDmQNTxV+kyOxN5FkD8nqHORXTs2exmXwZvvVBFSIqj4D2T K/zoNqhl5ttPxTwNeXL5oVM8liBG8ahYAm0MWnSVXHkwUrpAdrDk2IQ3KNd232hdMxYt MLFTTFCEPZUasdjYP+QgwE7PCdad0v5+Tecm62EjEZj4/PB2ZLn3G0FZFS6Nrtnrh9IF I32Dhfp1hC2dtjvTLE1NfbXmrElia4SXAjrhJOG27CRc4au8uwc/8PjRSMwhGfej4tH+ BQj59gIcRmXzpjN95JHnTLqkrhdWPtC6dptL3X7auce8eOI1h2M4vjaspLv06JXBL/Q4 sKBw==
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=ZbVHN6Ai7oSvkmk6pxZAW2SXDkr5YkqpAYbFFOcrcjQ=; b=SASj/OBuH63bR8u3kfZscnEFPyT9pKUq8xXsElxJ1Xygxj/Kkw2n0ax1dyYrbMCjeR 4QNYf+Zi+wvMjLioDQ6sWFNJjV8sqQq1HCdQyYLl3oCQMIEbD2qgHOFmBFTF7VuEVar+ kDCAoSv6IFSXHJOWIUzFNo512dv69dW9YtYHbcnNVY+KoGfwrpWxt/JG7GXleGi91Py/ 0owHu4ib+/td77DR+vrpzZL2Jhmt8U85ShYtNSYzcvbbZjH1/Xr/iqR1ldwjEVl1i9Sj DSD8QGg46AJMcp/UXBtrzoKumyX4Wrk6ilFNgbezi6FMVRjsGRUH9VX13HHes/SjgsTh vT1w==
X-Gm-Message-State: AOAM533qOvq+fOziIAz7qQFgkBLHcKQ12y+wEeUx+kbywxg6TR4CPbxi eFoqYQkQd3DiaJ4kJtSsbKghUxszfi20JzAi7gyihDLKPZA=
X-Google-Smtp-Source: ABdhPJxieUMZNjIArkNIJcuJkWW4H4mAM060QliypfwRMGDOW5O5hqsPt01mLQSrrPiJwK/dmnSD06GV0SOPHD8LBA4=
X-Received: by 2002:a19:5056:: with SMTP id z22mr2408284lfj.195.1590695689972; Thu, 28 May 2020 12:54:49 -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> <CALx6S34zxH2k=27uuGjOL8-bT5m2WTSBcxxHDmGAvejEsM6R9g@mail.gmail.com>
In-Reply-To: <CALx6S34zxH2k=27uuGjOL8-bT5m2WTSBcxxHDmGAvejEsM6R9g@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 28 May 2020 12:54:37 -0700
Message-ID: <CA+RyBmXpy++6sfo50AHdEzuOdYVVUXE4+7Tq3BJVSHG3nTJK0Q@mail.gmail.com>
Subject: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
To: Tom Herbert <tom@herbertland.com>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, IPv6 List <ipv6@ietf.org>, =?UTF-8?B?UmFuIFBhbmco6IGU6YCa6ZuG5Zui6IGU6YCa572R57uc5oqA5pyv56CU56m26Zmi5pys6YOoKQ==?= <pangran@chinaunicom.cn>
Content-Type: multipart/alternative; boundary="0000000000008bfe9d05a6bab34b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8-BZ1RgdtmrM7TAMTIksu_jKzyc>
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 19:54:54 -0000

Hi Tom,
you've noted that "The format of SRH is very specific that SIDs are 128
bits". True, that is the view, the current view based on the definition of
SRv6 and SRH in  RFCs 8402 and 8754. But both may be updated at some point.
Thus we can avoid the introduction of RH per SID length. Would you agree
that it is a viable option?

Regards,
Greg

On Thu, May 28, 2020 at 11:33 AM Tom Herbert <tom@herbertland.com> wrote:

>
>
> 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
>> <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
>> --------------------------------------------------------------------
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>