IETF Logo Mail Archive

Re: [spring] IPv6 Addresses and SIDs

Gyan Mishra <hayabusagsm@gmail.com> Mon, 14 October 2019 14:45 UTC

Return-Path: <hayabusagsm@gmail.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 9551012018D for <spring@ietfa.amsl.com>; Mon, 14 Oct 2019 07:45:34 -0700 (PDT)
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 cc8STpvhM3LH for <spring@ietfa.amsl.com>; Mon, 14 Oct 2019 07:45:31 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 AAFDF120170 for <spring@ietf.org>; Mon, 14 Oct 2019 07:45:31 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id n26so38389310ioj.8 for <spring@ietf.org>; Mon, 14 Oct 2019 07:45:31 -0700 (PDT)
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=krtjtBu6VKvZsYWnCBR8VfBIW6itd4MlC9irdIdemPU=; b=m1D6R4MMqPo/x76IDuUPSnqpR18S6hcjIws155q/4xfuD32EwC3k0amzNLYCKOisHw um0S6iwkH81WeAyU/3+DsSy4NA+N3j+5r0+v6Q8ENrUAakEHUR4tFbspf5Hj4CSdyJ73 6KrxLcTyWKmI3pvTZoHChvvov7mr2g1xnQPeAhrrJcq9qMYGO9xbYnTker7MS1svGg/x RguQdK3+r+I0D0cFnCVDqlZZ1b4xnnA8exW2qjYEZeBScMix1z2eqZzNRRDxqHGIEPyf npOBgwo7X32gL9WcT+hLrcEL5JN5h1Dre88Afff9F9EcSAp3FdUbTjDWAGqHh/zxOCnY AZTw==
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=krtjtBu6VKvZsYWnCBR8VfBIW6itd4MlC9irdIdemPU=; b=sNPuMtAGjrki368Ns1nL+MOnRKZ0dVJ0NzVidXuLGiUiFWIY24eKMJKpDX/0EthOsA pufj3sYlWrxw8zl4gBhAp7spdPmBY42I7Vu4jEyk+xxI+rieJagmMQ6dDZwB6VDJXnaF pqRm6kXGCmJ5xlOWpLsQKUxvurXuczo5ite/wG+Oczv9GGfIQkdPigMhQxq+BmyvqC8H uyqS7d7MTuIIN7Vfkw0de7L+RqrCKw/aLq4RuvGZiKPCSArYr8sYTyoR7/D5P8kue5WV wfk0WDfCKSMIu1q6ynYqO2/ClUREd8WrnQ67W/IYudwReSSno2R+km8sw46l0MpVmtYT W60A==
X-Gm-Message-State: APjAAAVHwVcPH5zJ8oblvK6cqEVeKUNc6JJBwC7sFs6f+6WCel1Yw4Kg qDGwIAdNX/w4x4sGNx9HBrKORBySsg7N+PrTx6Q=
X-Google-Smtp-Source: APXvYqwSjV6l8jvPpvnT29fSFpEup25uFapBwPiMqRXTJEwsg1rkJ4/+paFJ5+EM62Y25ocz9PPdEySrOQ7OVmNAylU=
X-Received: by 2002:a5d:83c1:: with SMTP id u1mr15845963ior.78.1571064330679; Mon, 14 Oct 2019 07:45:30 -0700 (PDT)
MIME-Version: 1.0
References: <SN6PR05MB5710CBAF8E6DF307401A2166AE9D0@SN6PR05MB5710.namprd05.prod.outlook.com> <f5eb739b-9ae4-433e-e6c0-8bcdb7bc575e@si6networks.com> <BYAPR05MB5703169601886283700608A5AE9F0@BYAPR05MB5703.namprd05.prod.outlook.com> <B6FE2A8B-B23B-4E9C-BB33-F6A5BD78C52B@gmail.com> <BN7PR05MB5699E5EA714CC64456771712AE940@BN7PR05MB5699.namprd05.prod.outlook.com> <1076F074-EB35-4D38-9949-4A241C946E07@gmail.com> <1fce4e24590847348894d10ca8bd5816@nokia-sbell.com> <D3FE1CA3-A8D1-4392-8EEC-CDCC7FC0827F@gmail.com> <BN7PR05MB56993D1127A8CA9CCC0E4A9AAE970@BN7PR05MB5699.namprd05.prod.outlook.com> <213BB95D-0E06-4E9A-B552-2A2466DC42AF@gmail.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>
In-Reply-To: <CAOj+MMFvA7sO1-1jSTRZQDNteH3UsaL0436b590hB54M6T1Unw@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 14 Oct 2019 10:45:18 -0400
Message-ID: <CABNhwV0ixZuJ35cWQ1kn+gO809wtk6hsO92qi6PpU9oDGxL_vA@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, SPRING WG List <spring@ietf.org>, "Wang, Weibin (NSB - CN/Shanghai)" <weibin.wang@nokia-sbell.com>
Content-Type: multipart/alternative; boundary="000000000000597d9c0594dfebc6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/LFHfxVQqpSejeixE1Zwd2SGaaQQ>
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 14:45:35 -0000

On Mon, Oct 14, 2019 at 10:34 AM Robert Raszuk <robert@raszuk.net> 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.
>

Ok did a google but could not find a draft on that please forward. So I can
see that is possible for intermediate nodes not necessary to be “SR aware”
I get that but what about the PSP or USP node that removes the SRH EH
header.  I would think that functionality requires that node to be SRv6
aware.

I looked on LSR WG and there is an SRv6 extension for ISIS and OSPF as I
expected. So since there are extensions related to IGP goes back to my
original question of SRv6 aware nodes.


https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-segment-routing-extensions/
>

  https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-srv6-extensions/



> --

Gyan S. Mishra

IT Network Engineering & Technology

Verizon Communications Inc. (VZ)

13101 Columbia Pike FDC1 3rd Floor

Silver Spring, MD 20904

United States

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com

www.linkedin.com/in/networking-technologies-consultant

v2.23.0 | Report a Bug | By Email