Re: [spring] How CRH support SFC/Segment Endpoint option?

Robert Raszuk <robert@raszuk.net> Mon, 25 May 2020 08:57 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 4F0433A045B for <spring@ietfa.amsl.com>; Mon, 25 May 2020 01:57:11 -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 slqOwKjIx-QS for <spring@ietfa.amsl.com>; Mon, 25 May 2020 01:57:09 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 9C7403A0440 for <spring@ietf.org>; Mon, 25 May 2020 01:57:08 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id l5so14398603edn.7 for <spring@ietf.org>; Mon, 25 May 2020 01:57:08 -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=rCPYYPggIx+mfkGcWbyjNRkjuOm6nVwow9dKQx0j2P4=; b=ZioHD11R0b4aXSqscmoHoEBaXpxPr7TPaEsbo3Pf0EE0WDaSpp7CGeUcN0846oSggP ikZiyPLgiIgO3CEPngrYeKds7M9mjmx2nr7Q6UGkke/mSZjT7Kq4AqO3lNffcS+yBhou oTLGSLGLVKmToXfObuAsIrEcGZ/lNlEAJrgqQGTHxXxIBugk9PcnbgXu7+0nS7cahrnH 9moyvNeORUzbLiXeUG0ME+BTh+xlyTWsmWkLepBZCoTZ19QGGUpBWAypSfVyj/svgNiv Wp2GVeuEPpRji4LChvYeTjhmR2jl5llgIjOoxYFcdtkSOg4kUv0NYwQ/aYQsCntM7P2B cBMg==
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=rCPYYPggIx+mfkGcWbyjNRkjuOm6nVwow9dKQx0j2P4=; b=QGEl0/f0mYKObVyLt++2ixx7MPmXTNYyXKko8xhUEiIf4eb4JF/3iyq85tc0qjWZd6 4s673YgFSzjB5wpf4Oy5o4kpGETPiDkVVKVBKQDxMHUqOggloycaWCAAPYUo14DE19+W xEBVshkhQYojThNfJGrrpZACrjIPlVCovhYtNZlWtPxGhXm+xg23N6DttMgEVkKKHiTc JNws0az6pbjQUtO7VvK4Wa6O7ABVFodA8KVAhZU/k0iezNovrQzMhRRNHs3PRdcSpkkx aIO880xHuAg61+/jNq07bcKk2eaW6y8FtUCyup60WHGoFw0elNZubwlo5X6YXLavU10W cTsw==
X-Gm-Message-State: AOAM530mKDW+IIMcG9q2OhfXnddk86wHl+1LI0GIkwK4XBPWNQ4rcOcm IdkvxM4hX5vLu89JgUkqfXPTsActZW9rsknuWDU73g==
X-Google-Smtp-Source: ABdhPJzkPobX0l/V5EUImtnaxsizcImudcwnC4RWCbUN4+b+l+kE5HdDiLFN/lRHVSHBwne3zuor5Ib6z8Gv8Sw3fPo=
X-Received: by 2002:aa7:cb8f:: with SMTP id r15mr14800176edt.120.1590397027018; Mon, 25 May 2020 01:57:07 -0700 (PDT)
MIME-Version: 1.0
References: <C7C2E1C43D652C4E9E49FE7517C236CB02A2CD12@dggeml529-mbx.china.huawei.com> <DM6PR05MB63482CFA4D5AB938D5A4B818AEB40@DM6PR05MB6348.namprd05.prod.outlook.com> <C7C2E1C43D652C4E9E49FE7517C236CB02A37DC6@dggeml509-mbs.china.huawei.com> <DM6PR05MB63489256A7C8357BEF526EE2AEB20@DM6PR05MB6348.namprd05.prod.outlook.com> <CAOj+MMGLj9OgFCcsB21oWXbcCqHZ7B4qTvCcrK9LXuKDYVu_vQ@mail.gmail.com> <CALx6S36yJ5CS6ykQhd_sW3T6=PjVJNOqewtg2joUtHnbsZPxSA@mail.gmail.com> <15815a80-7fe3-7d85-61a8-f7168a99cabb@gmail.com> <CALx6S35j=c9BUyyf1qs+As-51YVR6DTQAP+Xkc4zS05CGVJCHQ@mail.gmail.com> <DM6PR05MB63484B690AF323ACE5853D79AEB30@DM6PR05MB6348.namprd05.prod.outlook.com>
In-Reply-To: <DM6PR05MB63484B690AF323ACE5853D79AEB30@DM6PR05MB6348.namprd05.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 25 May 2020 10:56:58 +0200
Message-ID: <CAOj+MMGGZeZz2CHKQk_JhLVEZbKjFnpw_iEQ13hkahNScRgCSQ@mail.gmail.com>
To: Ron Bonica <rbonica@juniper.net>
Cc: Tom Herbert <tom@herbertland.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "spring@ietf.org" <spring@ietf.org>, 6man <6man@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d900f305a6752982"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/6JSy6FNCkJEiIdydWf3pT5IduII>
Subject: Re: [spring] How CRH support SFC/Segment Endpoint option?
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: Mon, 25 May 2020 08:57:12 -0000

Hi Ron,

So what in your opinion would happen with the below if there is no Routing
Header at all and I still modify DA at each segment endpoint ?

Can I still put two Destination options ?

Or reading the RFC8200 verbatim first DOH must be placed before RH hence to
have more then one DOH in a packet RH is mandatory ?

If so can it contain only 4 octets and no type specific data (so called be
a NULL RH) ?

What exactly tells the router to process or not to process last 4 headers ?
Is there a rule anywhere that unless RH is present and segments left = 0
destination must not follow next header in RH ?

Thank you,
R.


IPv6 extension header are ordered as follows:
>
> - Headers processed at every node along the delivery path
>         - Hop-by-hop
> - Headers processed at every segment endpoint
>         - Destination options
>         - Routing header
> - Headers processed at the ultimate destination only
>         - Fragment header
>         - Authentication header
>         - ESP header
>         - Destination Options header
>
> Note that the Destination Options header is the only extension header that
> can appear twice in a packet. The Destination Options header must
> immediately precede the Routing header or the upper-0layer header.
>