Re: [spring] Penultimate Segment Popping and RFC8200 (Was Re: We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping))

Robert Raszuk <robert@raszuk.net> Wed, 11 December 2019 08:29 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 AA62712022A for <spring@ietfa.amsl.com>; Wed, 11 Dec 2019 00:29:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 6mCjcuGnPjYG for <spring@ietfa.amsl.com>; Wed, 11 Dec 2019 00:29:58 -0800 (PST)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 0D209120802 for <spring@ietf.org>; Wed, 11 Dec 2019 00:29:58 -0800 (PST)
Received: by mail-qk1-x72e.google.com with SMTP id x1so18884196qkl.12 for <spring@ietf.org>; Wed, 11 Dec 2019 00:29:58 -0800 (PST)
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=N6EC+r77RCoadf9Tobelt+AU0hyT1x0Dsjjz04ueFPk=; b=J/vrBfG+VwLy7N7i9yJyIqwltnxRaLheSqNRjVII/V41yveuatKFqKI7Ai5FQektQ6 37iW4xq29f7LdthcaaJzGmTJLE16psIiuPVW2TkVsy5ySduUhIEE76xSEc/125xoXEpp QXJjZC7AylwHycd2gSaFHN6bIhuPoBAujESeohhrQbLMSMXgR5/CaJURDhUyjEWkKKna 5/tmFNL601DhNhBnqFRyvP2veNdY4JZGwpFxbNhZcCdT/NmQHzUj4rsl515Hzj9CTBxM u2CEB1rxeD8CLTgMFZiwMzSgNrypBEN7gjI34555KG0Q4xCKq68AfDWATqLociOpmCDv 6pmQ==
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=N6EC+r77RCoadf9Tobelt+AU0hyT1x0Dsjjz04ueFPk=; b=fjRHlERkc72Yo9xRqADBLU2MTIhJmrzX7irMPtSioL2KFg7Dc2AU4gEOGYiScKmtDz 2Oa+F3e5nCrbFgI4hKcbRrrvIIbZK8gM24gGb5Tmrcf6ooW0hKvZtPs3HjUmU7yeVC4F KfPb/3s9oUu+pl3Wf1Iiwf21R+SGorGZl9xA3J1f1aOt8g0isgcp+H1ayF+6v/DBxlHV uboB9se9L412zRXDLAzO43C2rHejxU3UfHBAObBVPiDFYbItJL+davtUeNhhT63E4sCH iTfVojwAv+dDDyGL8p6t/kEPwHwpF/a5FvHvMmIUdaZ6CLVpKbvq+7ePEml9s4KWjtIi KPRw==
X-Gm-Message-State: APjAAAWQt8cYMzIQJViScqMqHPdhv8r8Zu7NC2S/0D7qCNC27J38aMtX 0+DFItbx03nyi7RM4SaSogPAeWIyT6NLw/DkVg/oeg==
X-Google-Smtp-Source: APXvYqxye14TUu5wBTuD3t2v0nBFXTA51sFBxoCWOBUnfjYIpn4nnz1MX+uq3849PpsU8hODzz6lfpI3q8MT0/55VlQ=
X-Received: by 2002:a37:693:: with SMTP id 141mr1771722qkg.134.1576052996973; Wed, 11 Dec 2019 00:29:56 -0800 (PST)
MIME-Version: 1.0
References: <f2a0ad13-0eba-6f5a-1d3c-e45e2780f201@si6networks.com> <d59de54e-c7f8-be67-1e77-b051735d40a6@gmail.com> <3bce7b18-ea45-d29f-5dfb-1d3258b07d1e@si6networks.com> <c6e1f690-b0bf-9f45-8fa7-92ed182c5b04@gmail.com> <a2cc5cbd-ac06-e193-307c-3ffe5b21b0b1@si6networks.com> <80A78F48-9802-4DA9-B264-1A8920C1DDF9@kaloom.com> <c727fb5e-015d-90e2-9860-6c48ce021ac4@si6networks.com> <CAOj+MMEyMDHULL7Pr=QmucTJy9b=3ph9TgTZ7koi9BBLkFCJ6g@mail.gmail.com> <bb767aff-8737-a749-2f99-ac350f66def5@si6networks.com> <CAOj+MMEjzxrEbmKbUn11EsTSnVOZC0cKZhAeXapV2vW++g0ZdA@mail.gmail.com> <885c9ad6-ddd2-392a-7e9f-722509753e2d@si6networks.com> <27448_1575983799_5DEF9AB7_27448_30_1_53C29892C857584299CBF5D05346208A48D245CD@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <5b0f37d2-56a3-5f7f-ab29-7d6ebc2367d5@si6networks.com> <CAOj+MMHoAap_7XZs5HSO+a1C18guFzkg1fkov8Wo6ZqHj=xeHQ@mail.gmail.com> <603cbb85-3b68-5c93-e7c5-3768e6310f48@si6networks.com> <CAOj+MMH2rO_YSLrJDEA5G97ad1jMsJHtZDZ-xP+b==smk-J8Dg@mail.gmail.com> <26f2fff6-f6c8-0e9f-29e6-a180896f5a05@si6networks.com>
In-Reply-To: <26f2fff6-f6c8-0e9f-29e6-a180896f5a05@si6networks.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 11 Dec 2019 09:29:46 +0100
Message-ID: <CAOj+MMHDOgA54mMWq+ko72e9kW7jk=ut8M31c_XNvAx-hXt6qg@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: Bruno Decraene <bruno.decraene@orange.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, SPRING WG <spring@ietf.org>, "int-ads@ietf.org" <int-ads@ietf.org>, Andrew Alston <Andrew.Alston@liquidtelecom.com>, rtg-ads <rtg-ads@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ole Troan <otroan@employees.org>, Suresh Krishnan <Suresh@kaloom.com>
Content-Type: multipart/alternative; boundary="000000000000083df80599696f09"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/elylGdknOuPwUqaZpug-i30iJUA>
Subject: Re: [spring] Penultimate Segment Popping and RFC8200 (Was Re: We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping))
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: Wed, 11 Dec 2019 08:30:00 -0000

RFC 2473

Quotes have been already provided to the lists.

When encapsulating a packet I can put whatever EH is defined and when
decapsulating the packet I can remove any EH I inserted before. I "own" the
new IPv6 header. Very simple. It is like taking the cars on a ferry.

Your original packet (call it end to end ... call it original src going to
final/ultimate destination) is just a payload.

I can not believe that anyone can not grasp such basic concept.



On Wed, Dec 11, 2019 at 3:29 AM Fernando Gont <fgont@si6networks.com> wrote:

> On 10/12/19 18:50, Robert Raszuk wrote:
> >
> > By your books does RFC 2473 or RFC 4798 or 100s of other RFCs which
> > encapsulate IPv6 packets all violate Internet Standard I presume IPv6
> > spec ?
> >
> > One of us clearly is missing the point. I will let list members judge
> > which one :)
>
> Could you please point at any RFC that inserts EHs or deletes EHs at any
> place in the network other than the source or the ultimate destination?
>
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>