IETF Logo Mail Archive

Re: [spring] SRH scratch space (was Re: Question about SRv6 Insert function)

Erik Kline <ek.ietf@gmail.com> Tue, 10 December 2019 20:54 UTC

Return-Path: <ek.ietf@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 854F312011D; Tue, 10 Dec 2019 12:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=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 wtHllyBqdRot; Tue, 10 Dec 2019 12:54:33 -0800 (PST)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 083341200A4; Tue, 10 Dec 2019 12:54:33 -0800 (PST)
Received: by mail-ed1-x52d.google.com with SMTP id c93so17224653edf.7; Tue, 10 Dec 2019 12:54:32 -0800 (PST)
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=KRjo/HankN5vVOKEegiY7dmqS8jB3ybsromK4isR3bM=; b=N6HxObx5U1nZhDBH+CKHhnz9WZQg4aGKCcvd395/DrcNWbDd6DEQXaQxnavtcjLFnB 2vNYMvceazQ8fXQ4Ajnsa6erQrB99AhQc8NXRr6XIIuCZ5q5bnmyiImza9zdaJrObjqk nZP/VfkSSU7og+Ninf4vYyQeaGhkEZaR+F2QxlcSHC7ijR8jDH/fIblUODnn18+dxPKL dVQmQ/HPRCv81s+XD2j+XveSFeLLOoWUs6OEaJ67+Q/fqPBvHrMNN4Bbbvy85de8xhhh FZIRmRKRX10dNnvdDYwbL3r5pbco4L9Oyxoz0neiPN1CN1P74myCQPIH6B4THYrzy6tt fT+Q==
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=KRjo/HankN5vVOKEegiY7dmqS8jB3ybsromK4isR3bM=; b=XqiuKzZmOUHpLWSDuVAaDrertYvA0YnFcxajfd/HR+8/WaRqxflIOJmeBsR1ePGYnA fKt02fGdVrEAp76BxdOwdEIwYPJWdvSEoKyGiOYcgLatTqGlVau++JVdCuesj7PNAG3W 0xV9ovTjDSoSyWB43clbU8+5qvpZQPVI5PKQtL/hGulsM6OZA7j1h6236CEHoxTZ135l QJtOow3k9YuUiUPPFQR4XhVjPbeHmAjsm5NhpPvDKzyBrdKG1gmcGBEmRzoU0jW/fdDn DzffaQC7YGqcFUOyfbLNpnGWOwML4W0YwzuhFfih16LV1yXNwj5O2dJuWnTiwpt9xdTn cSZg==
X-Gm-Message-State: APjAAAV5M3dJTAcKgNqdqCQ+Nf/iuzZDWHKqHNV8sv43QFY837DsTgeq 1wtfyoG3qoJ1vhTuUPZ91sWoEs90NydzQ+ABsJzF/FlG
X-Google-Smtp-Source: APXvYqxCeGUU5L3gOTeG6agItdjL1XF9Ta473GnnfAuEZh0qEg6vqW7xT8LOEB7I2pYNHKe2Uz630EL7EaHQzdwhN44=
X-Received: by 2002:a05:6402:2d8:: with SMTP id b24mr40664120edx.67.1576011271667; Tue, 10 Dec 2019 12:54:31 -0800 (PST)
MIME-Version: 1.0
References: <HK0PR03MB3970C6DCC635E7CD802D65FDFCBD0@HK0PR03MB3970.apcprd03.prod.outlook.com> <BYAPR05MB54636A2332FED916A26A6F14AEBD0@BYAPR05MB5463.namprd05.prod.outlook.com> <3e31873a-278a-2154-0e71-4d820bba323d@gont.com.ar> <4012D854-2F10-4476-951D-FFFE73C5083C@gmail.com> <cb2f56f8-acdc-d68d-0878-9609cb3d7b1b@gont.com.ar> <28214_1567694772_5D711FB4_28214_238_1_53C29892C857584299CBF5D05346208A48BFA9F3@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <129bbb32-0f14-b799-430c-8f76fb6b1279@gont.com.ar> <1824_1575998223_5DEFD30F_1824_112_1_53C29892C857584299CBF5D05346208A48D24EBD@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <4384c08a-65f5-dbfb-85c7-8365feba9662@gmail.com> <CAOj+MME1+JXth8m4U_E5R6VLvurVR_y_DQvOBy7JmGxHZp7T=Q@mail.gmail.com> <CAMGpriV8BFjOed_-QJYEZc_BANvEuc1hRgYjSdaVUYygVzPj+Q@mail.gmail.com> <CAOj+MMHCA+=9zv_UJAF3gC6R1TWKb6LQJxaGsrRa0N7Amdxrww@mail.gmail.com> <CAMGpriWbz3Gf2UcNDigRVo8gEssdaL6HnH2_6Ln050gQFbFDYQ@mail.gmail.com> <CAOj+MMGuParGLAA9_2n1zihGjJsKHr+NOK3EXP3j87ibXqmhmQ@mail.gmail.com>
In-Reply-To: <CAOj+MMGuParGLAA9_2n1zihGjJsKHr+NOK3EXP3j87ibXqmhmQ@mail.gmail.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Tue, 10 Dec 2019 12:54:20 -0800
Message-ID: <CAMGpriVdDSw4FOk5ApQq935H5aes5OBH=L=hhGD_6U0wGBCA0A@mail.gmail.com>
Subject: Re: [spring] SRH scratch space (was Re: Question about SRv6 Insert function)
To: Robert Raszuk <robert@raszuk.net>
Cc: Suresh Krishnan <suresh.krishnan@gmail.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>, Fernando Gont <fernando@gont.com.ar>, Brian E Carpenter <brian.e.carpenter@gmail.com>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000002873805995fb8b5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LLB_vuW2eJd4LIqzOWOSHoAksMM>
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: Tue, 10 Dec 2019 20:54:34 -0000

Ah right.

Still, in terms of the things that could be relaxed in 8200, allowing the
SRH to be treated more like a Hop-by-Hop header might be more palatable
than things that change the effective MTU.

On Tue, Dec 10, 2019 at 12:42 PM Robert Raszuk <robert@raszuk.net> wrote:

>
> The issue is that RFC8200 forbids even modification to any EH unless the
> node is a destination node in top most IPv6 header.
>
>
> If there were no resolution to the insertion question vis a vis RFC 8200,
>> then would it then suffice to recommend that ingress nodes should include
>> some padding for these non-SR midpoints to play with (iff. the network has
>> such midpoints), and otherwise abide by RFC 8200?
>>
>

v2.23.0 | Report a Bug | By Email