Re: [spring] I-D Action: draft-ietf-spring-srv6-network-programming-06.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 19 December 2019 23:06 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 7D59C120089 for <spring@ietfa.amsl.com>; Thu, 19 Dec 2019 15:06:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, URIBL_BLOCKED=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 BY6mbQ2pikVn for <spring@ietfa.amsl.com>; Thu, 19 Dec 2019 15:06:43 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 40D2012001A for <spring@ietf.org>; Thu, 19 Dec 2019 15:06:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 47f6vR1RZ6z6GDFl; Thu, 19 Dec 2019 15:06:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1576796803; bh=Ye5mQzmsU/M1k/psk8mhNxtemDlVkW/jpgHirdQwi7I=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=nUXXghnLNhMXQOguXghS0F2TQQrHH7NinAvsea7HqdS4KDhLQJtAdNLlUak5E3wBl Q+TNPnZNFzMJTCwBWfgzshCThGe00PN069sn9jCOmkiMMVQlyllAzyz2HEHnJCS/zc 3Bp8P/EtTWbZ664HXf5L+fow6iPa0aqje7vfqLVY=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (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 maila2.tigertech.net (Postfix) with ESMTPSA id 47f6vQ4XjHz6GDCw; Thu, 19 Dec 2019 15:06:42 -0800 (PST)
To: Robert Raszuk <robert@raszuk.net>
Cc: "spring@ietf.org" <spring@ietf.org>
References: <157609408568.11496.11799785813274132900@ietfa.amsl.com> <4c762fc5-8a61-e182-a9cc-d45b0f586ccc@gmail.com> <3A12D735-7899-4679-8FC8-DF8875D40A62@cisco.com> <628e5dfb-7ba4-d841-ebeb-cfc52d7294f1@gmail.com> <ACEF56BF-B851-43B2-9211-B6C39C34DB63@cisco.com> <49b7e45f-a26f-cf4a-f8be-9aa917c34203@gmail.com> <CAOj+MMFBKFBxacT9Z=HR89U10d9=jG-b8ypx4ukQgb0EFfN=Uw@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <aef3f572-92a7-5fac-2ec9-8616a74fde13@joelhalpern.com>
Date: Thu, 19 Dec 2019 18:06:40 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAOj+MMFBKFBxacT9Z=HR89U10d9=jG-b8ypx4ukQgb0EFfN=Uw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/llEZFmVQWdHEeq61tiueoPK64Cs>
Subject: Re: [spring] I-D Action: draft-ietf-spring-srv6-network-programming-06.txt
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, 19 Dec 2019 23:06:44 -0000

Robert, you say we are operating on the encapsulating header.
Do things still work right for the case that the authors felt was 
important in the SRH document where the source and destination hosts are 
inside the SR Domain, and therefore there is only one IPv6 header?  (I 
would not be surprised if they do still work.  But your assertion in the 
email below, and the repeated mention that the encapsulated case was the 
only case during the header insertion discussion in Singapore leaves me 
needing to clarify.)

Yours,
Joel

On 12/19/2019 6:01 PM, Robert Raszuk wrote:
>  >   And where is it forwarded to, since we are already at the DA?
> 
> PSP operates at the n-1 segment end of the SR path so naturally after 
> swapping DA it is forwarded to the segment end. Note that we are all 
> along operating on the encapsulated header ... original packet including 
> its original IPv6 header is sitting as passenger here.
> 
> So last segment here will received encapsulated IPv6 packet will 
> decapsulate it and fwd based on the original DA.
> 
> Seems very simple :)
> 
> Cheers,
> R.
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>