Re: Header Insertion and TI-FA

Andrew Alston <Andrew.Alston@liquidtelecom.com> Mon, 11 May 2020 20:04 UTC

Return-Path: <andrew.alston@liquidtelecom.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 306973A0CB8 for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 13:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 YXkaV2WDce0l for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 13:04:37 -0700 (PDT)
Received: from eu-smtp-delivery-182.mimecast.com (eu-smtp-delivery-182.mimecast.com [185.58.86.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E96AA3A0CB7 for <6man@ietf.org>; Mon, 11 May 2020 13:04:36 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-am5eur02lp2056.outbound.protection.outlook.com [104.47.4.56]) (Using TLS) by relay.mimecast.com with ESMTP id uk-mta-57-eSwLkL_MNruTM0dCMoOOAA-1; Mon, 11 May 2020 21:04:31 +0100
X-MC-Unique: eSwLkL_MNruTM0dCMoOOAA-1
Received: from VI1PR03MB5056.eurprd03.prod.outlook.com (2603:10a6:803:bf::31) by VI1PR03MB4656.eurprd03.prod.outlook.com (2603:10a6:803:5d::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.26; Mon, 11 May 2020 20:04:29 +0000
Received: from VI1PR03MB5056.eurprd03.prod.outlook.com ([fe80::ed68:9303:79e0:cc49]) by VI1PR03MB5056.eurprd03.prod.outlook.com ([fe80::ed68:9303:79e0:cc49%4]) with mapi id 15.20.2979.033; Mon, 11 May 2020 20:04:29 +0000
From: Andrew Alston <Andrew.Alston@liquidtelecom.com>
To: "Pablo Camarillo (pcamaril)" <pcamaril=40cisco.com@dmarc.ietf.org>, Gyan Mishra <hayabusagsm@gmail.com>
CC: "6man@ietf.org" <6man@ietf.org>
Subject: Re: Header Insertion and TI-FA
Thread-Topic: Header Insertion and TI-FA
Thread-Index: AdYnknQqAO/1C9hyQECELexezObcNgABpa0AAAEH7OAAAS7FgAAA/LmAAAHloQAAAbTu8AANELAA
Date: Mon, 11 May 2020 20:04:28 +0000
Message-ID: <61DBEBF4-ACE7-40D6-B172-EF46B35BC838@liquidtelecom.com>
References: <DM6PR05MB6348FA1FC00258ACE4FDE444AEA10@DM6PR05MB6348.namprd05.prod.outlook.com> <CABNhwV3-dMPg6SAAEz+uWre-rj6j5=1JgyyQyKyz_qn7f7mJwQ@mail.gmail.com> <DM6PR05MB634848D379A428372C166DD4AEA10@DM6PR05MB6348.namprd05.prod.outlook.com> <CAOj+MMEBVA+yK9cFXSe=GVUeH01ipi++nwCRQU_nQCxsKhyvRg@mail.gmail.com> <1B1A2C98-20F0-43F8-A299-C839D14A245C@gmail.com> <CABNhwV3m+2+Wt2CHRRhznEvTZ5KQdounv0e=icfbs4VOcoU0Rw@mail.gmail.com> <MWHPR11MB13740F8547CF700EC38CE4F5C9A10@MWHPR11MB1374.namprd11.prod.outlook.com>
In-Reply-To: <MWHPR11MB13740F8547CF700EC38CE4F5C9A10@MWHPR11MB1374.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.36.20041300
x-originating-ip: [41.81.33.242]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: f29547b7-866d-4d6a-7217-08d7f5e68354
x-ms-traffictypediagnostic: VI1PR03MB4656:
x-microsoft-antispam-prvs: <VI1PR03MB4656227A7D4070B5D665EE57EEA10@VI1PR03MB4656.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 04004D94E2
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: hbbEIWEhO20EGgvuWsXKPE6VBDFQy5W9xPlU/mhbWtGFhj7z5c/wzBo0m0STiZEe1WRwV6cG1BAvk+j2Td9/8kNNSJ0M5+3voKaN0FM11rHl35KMKXim+rfBe6z6p24jK7tAFMMXV1XtEu8aHc5/u1GpSxqOr1PfJzwUu0kZptJ/7qtsaPrn8mpHOjUauIOCsLgNKP0ygtghlgspywAkGhdXH0iyWXELlT7NEuwS7rUCyeshAVaw5DCm1amd/4Uxob0CbGyxjOyeRONX3geTkinphc5yAQldGw8iWCQpO0yBFbYNN/ucsuwjS7lw6vsZnyByX9Bd2blBxVOWqHEGRCPxA/URtc+Px4ec975ME8OWl9CiQ2zcBNobyOY5Q1HmkuXGvkun22Vf0FG8FMVUqo3h2QPagmmmvpwFEhvYoGrfvKZ+0eCGKDQeHMmyZlBPnNieFYBMIsulWuoep9cpxkna6gOUn7pXQdqDr5U8viDCTAy4T0Pxo9rYYJAOL60cCvX0jmH2B7bNgdJGDpGzbIMBJunf/TWyXEwqtk6Wi08VCPp6qSqoUtquwrWcc6o82YUP/yCOC6+bN67O6u+3LS7TvKIdbq9aljtdUfzOhIo=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR03MB5056.eurprd03.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(346002)(366004)(376002)(39860400002)(136003)(396003)(33430700001)(478600001)(2616005)(110136005)(316002)(2906002)(6506007)(6486002)(966005)(53546011)(6512007)(36756003)(33440700001)(166002)(91956017)(66476007)(71200400001)(8936002)(66946007)(76116006)(66556008)(64756008)(66446008)(62860400002)(33656002)(8676002)(26005)(4326008)(86362001)(186003)(5660300002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: ESHW20092Kr9XMleN/Q2xqzAFnO/kyQUI/O7SA74GvZPSdGcsx0uNtsAmQs52umBbptOIAwbAviRDKdRkgqsN8dDQIskIfUlbMe1CDibeHD+YlWzPJv1GWAw/TypKaWhY2/6w48/NY1rtmBL+wDkVu1BEcrLR/6vkcxHqmZGq8IdVU4/0I+PcxcStnWCl7oUYih7b/yWZX5GfAabkVz1P/+EGxVxy1sWJPrXZ9pQdSVFdlSjwcwdBmoZ84hOO66t5mU4luCAXzuUdSkwPGSHTWIBoFMcIzoYz/AEI1Oz/ni4OR931Du0sTytQZNuhMWVipyikMFWpb88BhOjPlNF9djvC/qJQfRnFWSElnoLNgwYuXu1KIIRRt9aBHb0byDCkBd3+1N85jdF2BPEvXj+2Vyc/ePDxRGsTncWf1br+EKWBplOblZRyFoHxfn2OigSoV2AKyxsnBWrmgbkAdhv4RS0z20bzzCq8YDGTA2VQL8=
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: liquidtelecom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f29547b7-866d-4d6a-7217-08d7f5e68354
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2020 20:04:29.0567 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 68792612-0f0e-46cb-b16a-fcb82fd80cb1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: EFqDGwHk4bhcjGvWqwT6PZcOKf8yNL6HEVTv1bnYEI+8IAz/ovokXMEovPtFxsMCoPwzZbOEK28c8271uLMu7nsQyurd3eqW06GGeo9n828=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR03MB4656
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: liquidtelecom.com
Content-Type: multipart/alternative; boundary="_000_61DBEBF4ACE740D6B172EF46B35BC838liquidtelecomcom_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/MwS5LtHhlkCmqzpHh-_mLoRkij8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 May 2020 20:04:41 -0000

Hi Pablo,

While I fully realize that running code is not mandatory in the IETF – there have been numerous assertions about what is harmful and not harmful etc, and coupled with the deployment draft, I presume there is running code from the perspective of the authors.

Would you be prepared to disclose the release of code where SRH and this functionality is actually implemented – since I’d like to run a series of verification tests against it to test the effects on my network and I’m sure others would be interested in doing the same.  I can also then test against the Juniper implementation as tested at the EANTC and run my own inter-op tests and test the real effects this has on the network in a manner that makes sense.

Obviously however testing against a single vendor code is not ideal – and since the assertions are being made and in light of the deployment draft – I am figuring that you must actually have running code that is in the field? (I know on all code versions I have tested that are GA I have yet to see any SRH on any packet capture that I have done – hence I have been unable to do any verification testing myself against the claims made)

Thanks

Andrew


From: ipv6 <ipv6-bounces@ietf.org> on behalf of "Pablo Camarillo (pcamaril)" <pcamaril=40cisco.com@dmarc.ietf.org>
Date: Monday, 11 May 2020 at 20:13
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: "6man@ietf.org" <6man@ietf.org>
Subject: RE: Header Insertion and TI-FA

Gyan,

SRH insertion is NOT part of draft-ietf-spring-srv6-network-programming-15.
(SRH insertion is documented in draft-filsfils-spring-srv6-net-pgm-insertion-02 with a normative reference to draft-voyer-6man-extension-header-insertion-08).

> Spring - Please provide section within PGM that has the verbiage of the 6in6 encapsulation

This is already in the net-pgm draft (since rev 00). Please see https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-15#section-5<https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-15#section-5> .

Thanks,
Pablo.

From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Gyan Mishra
Sent: lunes, 11 de mayo de 2020 18:02
To: Krzysztof Szarkowicz <kszarkowicz@gmail.com>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; 6man <6man@ietf.org>
Subject: Re: Header Insertion and TI-FA


Krzysztof

So you agree with what I stated as the workaround.

Please read through exactly what I stated as the complete workaround.

If we are all in agreement with the prepend (6in6) encap) workaround can we have the PGM draft updated to reflect.

All

With regards to the 6MAN appeal,  the issues were PSP and this issue with TI-LFA from what I recall.

Was their any other issue outside of these two mentioned in the appeal that we need to address and come up with a workaround?

Thank you

Gyan

On Mon, May 11, 2020 at 11:09 AM Krzysztof Szarkowicz <kszarkowicz@gmail.com<mailto:kszarkowicz@gmail.com>> wrote:
Hi Robert,

If we have prepend, why bother with insertion at all? Prepend (6in6 encap) is much cleaner, IMHO.

Regards,
Krzysztof

> On 2020 -May-11, at 16:38, Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>> wrote:
>
> Hi Ron,
>
> > normalizing header insertion for the special case where the PLR is a segment endpoint
>
> When an operator is serious about good data plane protection with TI-LFA all nodes in the network will be enabled for SR. The less overhead required for the protection the better. You may just not have a room for adding additional 40 bytes to each packet at each potential PLR without fragmentation.
>
> Regarding all of your other TI-LFA related questions - I am sure Krzysztof will be happy to answer them for you internally :)  After all this is what your public demo was all about ....
>
> Best,
> Robert,
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org<mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<https://www.ietf.org/mailman/listinfo/ipv6>
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<https://www.ietf.org/mailman/listinfo/ipv6>
--------------------------------------------------------------------
--
Gyan  Mishra
Network Engineering & Technology
Verizon
Silver Spring, MD 20904
Phone: 301 502-1347
Email: gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>