IETF Logo Mail Archive

Re: [spring] SRv6 Network Programming: ENH = 59

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 09 May 2019 12:45 UTC

Return-Path: <jmh@joelhalpern.com>
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 C0DF412009E; Thu, 9 May 2019 05:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 LFhurei7JMk6; Thu, 9 May 2019 05:45:50 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D88FD1200B8; Thu, 9 May 2019 05:45:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 450CkP4dzcz11hCQ; Thu, 9 May 2019 05:45:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1557405949; bh=pJ9Nnlo+VxWaADTk9gCyQTgrni//Ccev6SkAvuFf6WY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=il05x0SRWaRF8wdABak5jw8t+Y6X5IZu3lXGTja3zo1U9awy8a+UMKP52EuhyI5Q5 /BMUuSdkKQNnwZ7N0UJO/p1h4KCTO1RAIykxFaSl88wUhV3kc8yNxiCtAO12CZpDzP g0bJrqfIrog9/14uIUjOgc5CyUAtTKk167TZvuPE=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 450CkN70Hdz11fmX; Thu, 9 May 2019 05:45:48 -0700 (PDT)
To: Ole Troan <otroan@employees.org>
Cc: 6man WG <ipv6@ietf.org>, SPRING WG <spring@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
References: <BYAPR05MB4245988C3A47C3665BD91172AE300@BYAPR05MB4245.namprd05.prod.outlook.com> <AA81898A-9E6C-4AD5-9629-4BA283378A79@cisco.com> <BYAPR05MB4245AEA785C959D29E4ECE61AE310@BYAPR05MB4245.namprd05.prod.outlook.com> <58529f07-acfc-3678-5381-4ae271143a45@gmail.com> <94EF12FB-0598-4E76-9A60-0CF67096DD04@employees.org> <CALx6S360dJD4_YcqMMy9k8NOLNdy1UZPAzBNOw1WpAz6iYfWag@mail.gmail.com> <CAO42Z2wBL=h=MKLshKUJa4m6aqTSGn4XQgKao06wKvvreKpB8w@mail.gmail.com> <CALx6S36q+7L7=7m_TgFJL5BN1ryM=9Kgb3sND1Rw+Pmza5OVYQ@mail.gmail.com> <DD003840-92D2-4878-B1CC-CDCB18FA527B@gmail.com> <BYAPR05MB42459C7A22F5AF2F1AB75CD1AE320@BYAPR05MB4245.namprd05.prod.outlook.com> <B2E808BB-E995-4AEE-A9E4-8AA7F92E4939@employees.org> <af4f15c1-bebf-8774-bb1e-d6643a8294b9@gmail.com> <BBDC17E6-31DD-40AC-A651-10362F41119D@employees.org> <4dd25f1e-a0b5-9382-eec1-788b4440658a@gmail.com> <79c8d47b-e8c1-a080-5881-9dc1e3adc8ff@joelhalpern.com> <DB4FEBBB-E629-49AF-9578-DAA40A8A9C76@employees.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <275e5796-53ee-0e04-13da-bc52f93919d3@joelhalpern.com>
Date: Thu, 09 May 2019 08:45:48 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <DB4FEBBB-E629-49AF-9578-DAA40A8A9C76@employees.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/uZ2NWLU-f0y_Ce2I7cFQuk3-eaE>
Subject: Re: [spring] SRv6 Network Programming: ENH = 59
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: Thu, 09 May 2019 12:45:52 -0000

No next header means exactly what the original request, and the 
documentation, says.  There is nothing in the packet past this IP 
header.  It does not mean that there is some next header defined by some 
other context.

Yours,
Joel

On 5/9/19 8:36 AM, Ole Troan wrote:
>> I think it is equally important to note that given an existing way of encapsulating Ethernet in IP, one ought to have a good reason for creating a different one.  There is no indication that this use case needs anything different than next-header 97.
>>
>> And Ole, no next-header does not, as far as I can tell from 8200 and its predecessors mean "the end of IP processing."
> 
> Huh? What do you think it means then?
> 
> Btw, here is the original request for the no-next-header:
> 
> Date: Mon, 28 Nov 1994 14:46:50 +1100
> Message-Id: <487.785994410@munnari.OZ.AU>
> From: Robert Elz <kre@munnari.OZ.AU>
> Sender: owner-ipng@sunroof.Eng.Sun.COM
> Precedence: bulk
> Reply-To: ipng@sunroof.Eng.Sun.COM
> 
> If I wanted to send an IP6 packet without any TCP, UDP, ICMP,
> or similar, data, just, say, end to end options, or something,
> which may be useful for sopme purpose or other in the futuew,
> what do I stick in the next header field?
> 
> The length from the packet header will indicate that there's
> nothing after the last processed header, but just sticking in
> a random "next header" value and relying on the length field
> seems wrong to me.
> 
> Alternatively, can someone say that its illegal to not have
> one of the transport level protocols in every IP6 packet,
> and will be for all (relevant) time?
> 
> kre
> 
>

v2.23.0 | Report a Bug | By Email