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

Krzysztof Szarkowicz <> Sat, 16 May 2020 06:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 072973A0784 for <>; Fri, 15 May 2020 23:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Yw93v51hJF_G for <>; Fri, 15 May 2020 23:15:04 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 85A8A3A0783 for <>; Fri, 15 May 2020 23:15:04 -0700 (PDT)
Received: by with SMTP id 50so5780784wrc.11 for <>; Fri, 15 May 2020 23:15:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=V1Tr9Hf+nIPk1adrYlUJG8UTAfKy3uel8U35g8hjq9s=; b=qTEM6ku9ZOTVlD4yUbND1iFdRx6jrgbASD65bK05CoDyL8EvjHHXX+0nHTBeurseDu 1Q+OL5eltj3zhd9BW886i7VCx2nETGOh7PmTPWAIJPd7KpDNw3pTHfyTQ4hj1nJpQA5A Vg+8Nl4QLLJjxVyeWKPdUdllOQOYYBA6+OkY6CSIqRQ/Y2x9rnATGJEVYLDc+y+/jn6r m0Mvr0IM9uH4cbynqUtu7jKyN3R5TR+JlDWLgOt6eWSvVAVVyuEL+n6FnhAWmapNUUyN b/n5uYUDmcEaIU5M+6fhUvuuQmBrQmXi9hFjQm8J12XgxsUrF/JeM18Xr02/euXzDL6o gBtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=V1Tr9Hf+nIPk1adrYlUJG8UTAfKy3uel8U35g8hjq9s=; b=MD6rPslBSrXHxjRSAymXySmrzSa8F0EAwxLD5hRpvvAYphRArm066YQ9CeXE3tsfyv HvkZUGyGfVMVOYzp3R/1asEBpxfiMMBwu+daWu+5Q8yHza6xJl9r570bcwCIsw2ueRnP jS70YUvGqGMDKS2GLHVHwxH05Mak0qDviRl3Dd4bsJAsriFDKIkQZLWwIWdCg4eDlg+K 0/w0ndJDFld8A6Fx5jWB7Rt+H27cPBqt1uerXc84tkDB+5De66hngfi1Vy40XXnXfUQ3 Z0DR8QLHlt5UYHwO2oDeSgIKDFLRm19XU7OVA+VBgw2WF1WFze3nkRnGG5B5WT4n8BlD 4UlQ==
X-Gm-Message-State: AOAM531HJPZmoYOCuQAhsycxy5VsePyplxVbl9y/UBc9xnesVuPi12/+ 4P7vTvuQ68LdttxGHT6sY0jY2koa
X-Google-Smtp-Source: ABdhPJyHCOA5fvkVEI5BTpGhKA7dtb5vcrUFZEhaO32726dSK3dHyW79iRjqrST9WPWOx+qz8fNjng==
X-Received: by 2002:adf:e4d0:: with SMTP id v16mr8107625wrm.294.1589609702255; Fri, 15 May 2020 23:15:02 -0700 (PDT)
Received: from ( []) by with ESMTPSA id 37sm6904452wrk.61.2020. for <> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 May 2020 23:15:01 -0700 (PDT)
From: Krzysztof Szarkowicz <>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Subject: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
Date: Sat, 16 May 2020 08:14:59 +0200
References: <>
To: IPv6 List <>
In-Reply-To: <>
Message-Id: <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 16 May 2020 06:15:06 -0000

I support adoption.

CRH is extremely simple, containing only few fields (most of them are mandatory in any routing header anyway), making it very easy to parse. It has experimental deployment, and both ASIC and Linux based implementations. Is very compact (six segments fit in a 16-byte CRH), and inline with overall IPv6 framework (e.g. AH). And, it has applicability beyond Segment Routing.


> On 2020 -May-16, at 00:13, Bob Hinden <> wrote:
> 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
> 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
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> Administrative Requests:
> --------------------------------------------------------------------