IETF Logo Mail Archive

Re: [spring] IPv6 Addresses and SIDs

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 14 October 2019 15:18 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 D6DCB120103 for <spring@ietfa.amsl.com>; Mon, 14 Oct 2019 08:18:37 -0700 (PDT)
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 IvA7QwFhRqms for <spring@ietfa.amsl.com>; Mon, 14 Oct 2019 08:18:36 -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 68A0712002F for <spring@ietf.org>; Mon, 14 Oct 2019 08:18:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 46sMdm2P24zsWXt; Mon, 14 Oct 2019 08:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1571066316; bh=L28W1KYiRLCe8t2+AMu6PNN6/2C+IOOAlhe32yF2fo4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=dsU2R2N4v4HCAoPACcMjXc/oFk3Bo5N1T50Uf0mbz1YZ+4X+1xHjbY83+7fS9rjzB SXPpZXOMZu3/JoLiQs5473Og+O+S+RsTs18fhgO3p5TxeF0vjqt0OUoVvS6AuyyqKE QQ+IbpMjcHhIeDmix3v5le3B++Sa80DJXw/z1RoM=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.20.7.244] (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 46sMdl5WTDzsWXr; Mon, 14 Oct 2019 08:18:35 -0700 (PDT)
To: Robert Raszuk <robert@raszuk.net>
Cc: SPRING WG List <spring@ietf.org>
References: <SN6PR05MB5710CBAF8E6DF307401A2166AE9D0@SN6PR05MB5710.namprd05.prod.outlook.com> <04711680-e9c4-1159-58af-609517ee8bdf@joelhalpern.com> <CABNhwV3SyZNY6GrJF+wpgTmpM6DSts4gXQgdFTEgWfN876u5WQ@mail.gmail.com> <CABNhwV1Ym_AG7svmPUpmjGz600QyGRvtY5xNP0_K-hoGewUGTA@mail.gmail.com> <424b13a9a9bf4802b57c0609c92baad2@nokia-sbell.com> <BN7PR05MB569958ADB8E7BFF6C7EBC56AAE910@BN7PR05MB5699.namprd05.prod.outlook.com> <CAOj+MMHcTyCyO5Z3KyP5otW1Xgq7un2ypEGtjjWpr00j2t9dGw@mail.gmail.com> <BN7PR05MB5699B5C42BDBD5BF244CB4A8AE910@BN7PR05MB5699.namprd05.prod.outlook.com> <CAOj+MME70PYa7mkTRPKHqhg_1cMAvHLU0qZJx-=CjVy-ZKXpAA@mail.gmail.com> <BN7PR05MB56999C4E2F2D8E045D47E3C1AE900@BN7PR05MB5699.namprd05.prod.outlook.com> <5ae3ab05035f439db46fe5126b1476db@nokia-sbell.com> <CABNhwV1DFaGdCjyKOCXVdMjZQK1R=diq4GeZqrR-_BMFHjcdvQ@mail.gmail.com> <CABNhwV35zdBzLjLHa6rL7Zr4V3=24x4is72DbzL6V0EG-WgUSg@mail.gmail.com> <CAOj+MMFvA7sO1-1jSTRZQDNteH3UsaL0436b590hB54M6T1Unw@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <86830cac-2277-fee7-38ca-a24caabf433b@joelhalpern.com>
Date: Mon, 14 Oct 2019 11:18:34 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAOj+MMFvA7sO1-1jSTRZQDNteH3UsaL0436b590hB54M6T1Unw@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/UoPBeTjDGbVu6S8b42mp1bKNNeU>
Subject: Re: [spring] IPv6 Addresses and SIDs
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: Mon, 14 Oct 2019 15:18:38 -0000

The SRv6 base document (approved by the 6man working group) does include 
additional behavioral requirements for all nodes in an SRv6-enabled domain.

Yours,
Joel

On 10/14/2019 10:34 AM, Robert Raszuk wrote:
> Gyan,
> 
>             __ [Gyan]  Spring WG  -??  Because SRv6 uses the same IPv6
>             data plan as "Business as Usual" NORMAL IPv6 traffic use
>             case of the "internet"  so the an "SRv6 enabled router" that
>             has the code that supports SRv6 has the software feature to
>             perform the PSP & USP but lets say the packet hits a node
>             that does not support SRv6 then the PSP & USP won't occur
>             and all the EH headers inserted for SRv6 routing header type
>             4 will remain in the packet to the end destination.   How do
>             we deal with this issue.
> 
> 
> 
> It's not an issue so we do not need to "deal with it".
> 
> SRv6 architecture operates just fine over non upgraded (read non SR 
> aware) IPv6 nodes.
> 
> r.
> 
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>

v2.23.0 | Report a Bug | By Email