Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)

Fernando Gont <fgont@si6networks.com> Thu, 05 September 2019 12:06 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 088191200C1 for <architecture-discuss@ietfa.amsl.com>; Thu, 5 Sep 2019 05:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ZfJ2q12YGP9c for <architecture-discuss@ietfa.amsl.com>; Thu, 5 Sep 2019 05:06:22 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673FF1200A1 for <architecture-discuss@ietf.org>; Thu, 5 Sep 2019 05:06:22 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-25.home.otenet.gr [94.69.228.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 828DB861CC; Thu, 5 Sep 2019 14:06:19 +0200 (CEST)
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, architecture-discuss@ietf.org
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com> <4a9df8af-c19d-42f7-0760-4e23d15d12d0@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <e61034c3-6d6c-51da-9252-17e53ebbfbd4@si6networks.com>
Date: Thu, 05 Sep 2019 15:06:11 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <4a9df8af-c19d-42f7-0760-4e23d15d12d0@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/3-a7DkuSPv1qdbY4MdnvNHjAVgw>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Sep 2019 12:06:24 -0000

On 5/9/19 12:08, Alexandre Petrescu wrote:
> 
> 
> Le 05/09/2019 à 02:47, Fernando Gont a écrit :
>> Folks,
>>
>> There seems to be ongoing working group item in the spring wg
>> (https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-01)
>>
>> that essentially proposes the insertion of IPv6 Extension Headers by
>> middle boxes in the middle of the network, which goes against a very
>> explicit requirement in the IPv6 spec (RFC8200) -- that notes that EHs
>> cannot be inserted in the middle of the network.
>>
>> This begs a number of questions (e.g., how come that one wg is working
>> on something that goes against a spec that is not under its charter).
>>
>> But given this is an architecture list, I wonder if anybody has a say on
>> the topic? (including the IAB). Is that the way IPv6 is expected to
>> work? What can we expect from IPv6?
> 
> Can we expect IP at large to touch headers of end user packets?  No. Can
> we expect it in a 'limited-domain'?  Yes, and I'd say INFORMATIONALly.

Spoiler: You can't guarantee with 100% certainty that packets will not
leak out from a "limited domain".


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492