RE: Header Insertion and TI-FA
"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com> Mon, 11 May 2020 17:10 UTC
Return-Path: <pcamaril@cisco.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 4D88A3A0B1E for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 10:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level:
X-Spam-Status: No, score=-9.596 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=KyPRQLiC; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=zzLEg/ax
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 EGLZlkgKYH8T for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 10:10:35 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27BF53A0AF4 for <6man@ietf.org>; Mon, 11 May 2020 10:10:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17838; q=dns/txt; s=iport; t=1589217033; x=1590426633; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=v2Im1kGi33t8lVlJNMVYR0it6C/YafGc7G37QzfAORA=; b=KyPRQLiC9v5lT8BSNXhn+tytXCSKYHNl4VjE/a47TDxIrAsYrEuOPuVa p46gP4jLewYucurjOpLOuV9sEMlHV+7Luv2Fwu0vqgngOZTUtUTl8MEwk JNRDlk8OLs0RTt1Xwze+New4CZYvnKEmnhpyyvvZA+5JFoFPWwHq2D0FS E=;
IronPort-PHdr: 9a23:Lq9w9xNiEsrjipDAlaUl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEvKwx3lDMVITfrflDjrmev6PhXDkG5pCM+DAHfYdXXhAIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtaHc//YxvZpXjhpTIXEw/0YAxyIOm9E4XOjsOxgua1/ZCbYwhBiDenJ71oKxDjpgTKvc5Qioxneas=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BdAQBPhrle/4gNJK1jAxwBAQEBAQEHAQESAQEEBAEBgXYEAQELAYEkL1EFb1gvLAqEGoNGA41BiXqJWoRjgUKBEANUCwEBAQwBARgBDAgCBAEBhEQCF4F3JDcGDgIDAQELAQEFAQEBAgEFBG2FVgyFcQEBAQECAQEBEBEKEwEBLAsBBAkCAgEIDgMEAQEBJwMCAgIZBgYLFAkIAgQOBQgagwWBfk0DDiABDqQuAoE5iGF2gTKDAQEBBYUqDQuCDgMGBYEzAYJiiWEagUE/gRABQ4FPfj6CHkkBAQIBgS0BEgEjBBEKBQcJEYJNM4ItjkqDCIYeim+PRkoKgkqIG4s7hG+CXIhnhQGMdpl3gkeRCQIEAgQFAg4BAQWBaCNmcHAVO4JpUBgNkEAJGoNPhRSFQnQCMgMCBggBAQMJfIx3AYEPAQE
X-IronPort-AV: E=Sophos;i="5.73,380,1583193600"; d="scan'208,217";a="764846151"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 May 2020 17:10:32 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 04BHAWMM004410 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 May 2020 17:10:32 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 11 May 2020 12:10:32 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 11 May 2020 13:10:31 -0400
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 11 May 2020 12:10:31 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GSNYguAz9f85SQJNbO+WPo1IJzTYtN90fspf37g6hPMc2LweT3VRH775KN/UWIsneXpQZ97DXa7B1SwagV5bdFzn98Ec84wrF8AQ4yJZlcrPmqrWX+zf2Km1zDw7Lq0Rv4r3X5cDNesKev142b4uiWrVuVqlxfRg0eXPrMqPdXQZGzfL63kqvEJoemIHcantL3MjTeP5L0802klZ3jNA3JjC04ftTqEo96e1jg+ELpPclggQPyDG82AFtqjcYbojlU4gkIO9yo6gKDeES+hcZso+A9u+HlBBTDO6Sbk8pMzxWL5GKHfcZXFybe2QGpOVvwsY+hnwa6tY222afSYRCw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=v2Im1kGi33t8lVlJNMVYR0it6C/YafGc7G37QzfAORA=; b=eSO0O5lci5kG3zJeAc1EerBqGE0Yec9M9GCTpMPdAKNZWWAbZPcCwcjaT2ykLh+cHCQuF0JtNjmWrUHNvRJ36mySV79lj2aXasrLaOaEK1VfEXfmHAhKUM5bTw/YJwZzKEojhrCfNnp9KltcMCGzgNF2toa7Ie5Oe11Kare3XpqZ/ZUH9SymQpYga0lCqzV4x4mTbVryd88ZlSNc2wPbfbxgSgYtZuLLoWblytNvam7ArFnMYi83R4SGr/Qe9zpmj746NIjSW9A8YL8u+b+hN4XiZEu7NgoWaU+L67+1644ghLxe/72dLRQne2VSQn6hz8lQGWnR3ilmfWzNQ7bbmA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=v2Im1kGi33t8lVlJNMVYR0it6C/YafGc7G37QzfAORA=; b=zzLEg/axJ3UQ/Sg5oik38NO0TSiTa5jK9q4+4zK3oPQwu22XYmIF0niqqqq9DYLQ/wu3HqM8AnJAym3ZMljMpkkWobeLs3LvVIMBFRMLj05JwpEADyMGqsn3Lb5wA9sYvWn4UVZYxQCkoyUyCAq1q/VFqdnbevpNmEJcmZo2mrg=
Received: from MWHPR11MB1374.namprd11.prod.outlook.com (2603:10b6:300:24::8) by MWHPR11MB1822.namprd11.prod.outlook.com (2603:10b6:300:111::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.34; Mon, 11 May 2020 17:10:30 +0000
Received: from MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::3919:ef10:f837:9efc]) by MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::3919:ef10:f837:9efc%9]) with mapi id 15.20.2979.033; Mon, 11 May 2020 17:10:30 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: 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/LmAAAHloQAAAbTu8A==
Date: Mon, 11 May 2020 17:10:30 +0000
Message-ID: <MWHPR11MB13740F8547CF700EC38CE4F5C9A10@MWHPR11MB1374.namprd11.prod.outlook.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>
In-Reply-To: <CABNhwV3m+2+Wt2CHRRhznEvTZ5KQdounv0e=icfbs4VOcoU0Rw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [173.38.220.36]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cdd55394-847c-4073-4d7b-08d7f5ce3584
x-ms-traffictypediagnostic: MWHPR11MB1822:
x-microsoft-antispam-prvs: <MWHPR11MB1822F5C7ECA7174C0DCF165BC9A10@MWHPR11MB1822.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 04004D94E2
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 8FvKC4SCrZy+IGaY4GLDLrCJwR1FxcbKhIcf+IlA8OhGaC2a0OBA5oLNJBtCX+z147OggZXBFP1U7OCkkF2Y/BDDg7wa64F19wqQQBlwk3YKUN1x1E4SDiltVerJNJRa04cDLNM9Uud6jkpXJQRPKAwhuPm7NOLEByEtkTlyCJdmfZjfcZjh4KD9PRFFX5f8EWt10KA3BLfps9dx40Kej3APoZCzuHsIStkGCrR6KINQu5qsq1+T1EBPy2Pb9+3LDhUpgz1Uu8kD0f4A30dXD+myPtROzGUFqCIeSgkzhgGGNGN2UPCzhCUQVRRjYhGIJnz4OcLK5viFRyI/CZNUcyICzApJnSMLjmodVPRE8X2kLlRin73B6IJiBNkAmlr2P3rC7mmhEYso27kclWGAfbmWB3gUp3JKHAmoOzzxpGC3GrXlibQ/fbG6CH4bFnJduWlIWQuPNMttYYrGAtuO8dNJEJ2keACF2JPd4sFsK+n24emwZ8mMQFmZmjYgWU/mFIiQhYL9trZ20+qEHDqXtXEgRIkaZO8TyYhREeqLXw/J/6rk6GqmeswKwTjGDdQRcG+XHUwrCfUp2FFz4WfIEGKeIexAZ+UI9YO7mcUIVHc=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MWHPR11MB1374.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(366004)(136003)(376002)(346002)(39860400002)(396003)(33430700001)(6916009)(966005)(71200400001)(478600001)(52536014)(6506007)(53546011)(33656002)(66556008)(66476007)(66446008)(66946007)(64756008)(5660300002)(76116006)(186003)(26005)(55016002)(9686003)(316002)(2906002)(166002)(33440700001)(4326008)(86362001)(8936002)(7696005)(8676002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: TcbIAG2xeHqGRAV/ockqeLKJP3LUAkHQF12nq2xTcXHs4cfMKh2tR2wvRPsiTXTVKKgBL83ome9BcEBk2S5cbR/vl5MJTd1NJ282q3yZJzz4kFQMzRBGt1Pvr1e3QHvYHZ9PK87VvTWJq30VBtiAaXgK03aJXEOSsyCC3corVoL+DPmNAHeC1oj36BkKK6JHWeuY5zZfUdwPudC8jlOh1Vox7lUJ5Je5CNQQJWiO6AYJtU3QOd7hbtUdg6uBOGag3cgdA/BxXC6z8L+etLljwNfa/obO5KnOTtkBjyWfA3hZJtEPnYLUJVvVSyeqBuYnt6sBQ6SrofhHPNm/p4osNk2niSQvJM7XD5XlzVR6Wn97oraZy9RGi5BY/YJZBYkjo0kIhjpCXVi80VFSDhiLW6Cm0iQacW2yyzadvxFICXFSwQwSzi+I6+9S+i8abFtAyL/L+uPp0i6xOXC9qghl1mEIRosu1TF4uTHAykKvcow=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR11MB13740F8547CF700EC38CE4F5C9A10MWHPR11MB1374namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: cdd55394-847c-4073-4d7b-08d7f5ce3584
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2020 17:10:30.5116 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: osMNLQdCTrw3k61lzn8s+UtLSAy93QA29KOOokucUdlHmb4e0mXsErhxW9pBbu2MAKXvbipkzRXuh2mCyFFNxg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1822
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/r4_cEZWopbzFJOULOFul2_m-BLc>
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 17:10:48 -0000
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 . 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 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org<mailto:ipv6@ietf.org> Administrative Requests: 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>
- Header Insertion and TI-FA Ron Bonica
- Re: Header Insertion and TI-FA Gyan Mishra
- Re: Header Insertion and TI-FA Gyan Mishra
- RE: Header Insertion and TI-FA Ron Bonica
- Re: Header Insertion and TI-FA Robert Raszuk
- Other use cases for header insertion (was Re: Hea… Tom Herbert
- Re: Header Insertion and TI-FA Tom Herbert
- Re: Header Insertion and TI-FA Krzysztof Szarkowicz
- Re: Header Insertion and TI-FA Gyan Mishra
- RE: Header Insertion and TI-FA Pablo Camarillo (pcamaril)
- Re: Header Insertion and TI-FA Andrew Alston
- Re: Header Insertion and TI-FA Andrew Alston
- Re: Other use cases for header insertion (was Re:… Brian E Carpenter
- Re: Other use cases for header insertion (was Re:… Mark Smith
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Header Insertion and TI-FA Gyan Mishra
- Re: Header Insertion and TI-FA Mark Smith
- Re: Other use cases for header insertion (was Re:… Nick Hilliard
- Re: Other use cases for header insertion (was Re:… Tom Herbert
- Re: Header Insertion and TI-FA Andrew Alston
- Re: Header Insertion and TI-FA Gyan Mishra
- RE: Other use cases for header insertion (was Re:… Ron Bonica
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Other use cases for header insertion (was Re:… Stewart Bryant
- RE: Header Insertion and TI-FA Pablo Camarillo (pcamaril)
- RE: Header Insertion and TI-FA Pablo Camarillo (pcamaril)
- RE: Header Insertion and TI-FA Andrew Alston
- Re: Other use cases for header insertion (was Re:… Toerless Eckert
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Other use cases for header insertion (was Re:… Brian E Carpenter
- Re: Header Insertion and TI-FA Brian E Carpenter
- Re: Other use cases for header insertion (was Re:… Mark Smith
- Re: Header Insertion and TI-FA Mark Smith
- Re: Header Insertion and TI-FA Robert Raszuk
- Re: Other use cases for header insertion (was Re:… S Moonesamy
- Re: Other use cases for header insertion (was Re:… Stewart Bryant
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Other use cases for header insertion (was Re:… Stewart Bryant
- Re: Other use cases for header insertion (was Re:… Tom Herbert
- Re: Other use cases for header insertion (was Re:… Uma Chunduri
- Re: Other use cases for header insertion (was Re:… Fernando Gont
- Re: Other use cases for header insertion (was Re:… Uma Chunduri
- Re: Other use cases for header insertion (was Re:… Fernando Gont