IETF Logo Mail Archive

Re: Extension Header Insertion

"Darren Dukes (ddukes)" <ddukes@cisco.com> Mon, 09 December 2019 13:32 UTC

Return-Path: <ddukes@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 A2F15120089 for <ipv6@ietfa.amsl.com>; Mon, 9 Dec 2019 05:32:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Spe34XVo; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=sV3Zl2Qj
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 utS4LoTH-Pvi for <ipv6@ietfa.amsl.com>; Mon, 9 Dec 2019 05:32:48 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29BA012007A for <6man@ietf.org>; Mon, 9 Dec 2019 05:32:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5429; q=dns/txt; s=iport; t=1575898368; x=1577107968; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=WDNtuoNS6ASP5ubAAyEX5hFfhSgUq7qvrsL54Fblwt8=; b=Spe34XVohr+lQ6kuGCm/Jf+RjCpGoj7wfWlc6srme53SFcaq0Nl85JeF LH2LtkBx535LzETX6wlu1cZ4sB6TRpOio7d3YFs5xnX61BZNyRSztyRRR nFwboa0gWqsYOFL72oHA24UeJbFZnJb02qZ9lp9wG0pJWhYcqEZ3HFVba 0=;
IronPort-PHdr: 9a23:oIfVWBOvtvE24f4adeYl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEuKQ/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBj3IOPpYjcSF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C5DADuS+5d/4wNJK1kHAEBAQEBBwEBEQEEBAEBgX6BHC9QBYFEIAQLKodIA4sBToIRkyOEYoJSA1QJAQEBDAEBLQIBAYRAAoIZJDgTAgMNAQEEAQEBAgEFBG2FNwyFUgEBAQEDEi4BATgPAgEIEQQBAS8yHQgBAQQBEggahHpNAy4BAqAbAoE4iGGCJ4J+AQEFhQ8YghcJgTaMGBqBQT+BWIJMPoJkBIFjg0CCLJV3iVCPFgqCLpYBmjKOSporAgQCBAUCDgEBBYFpIoFYcBWDJ1ARFIxmg3OKU3QBgSeNaQEB
X-IronPort-AV: E=Sophos;i="5.69,294,1571702400"; d="scan'208,217";a="676991862"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Dec 2019 13:32:46 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id xB9DWktm029915 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Dec 2019 13:32:46 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Dec 2019 07:32:45 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Dec 2019 07:32:45 -0600
Received: from NAM04-SN1-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.1473.3 via Frontend Transport; Mon, 9 Dec 2019 07:32:45 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=n1WJM4o+hAyH3QPOBPjkFPjQL+WXbpNlGSyYs6Z4CdELPE23eu9HrkdgOSi6YMuQVWX5IXFzgSzu8O2rCR+pnol/qDgPaQEUQMQ4Adxea1aXCkzmJv+HSrwoTcDfYiptQf6t/NXzL/NsuNNLjAbFltjgTV1qjBKwk2p56CVPGb5vohwuQRWzct7VbSq6pn/skl0uWd/V51UQB+C7BqDmWqNpdfE4CUMd46z6qEDNcWe79bpEYA/VPZHUVwm0UpMIvzUFMWH1bnMtYAoO+WU2/xF4neBGWnTDzRHDZvM9FKQ0dfFwZat41pmvR626Ms9QhKEPB3CkVhcsN0H/kANqJQ==
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=ZuWZ8w4oPGI2Wbx9ctlwKjAwIeW0NZ1TQKXIvzYxzbo=; b=gIBSnrIm9QpzOq32xmAsQ1pqbiqG8JJClwyOsMk0CJI9faNiMJ6zr5NTzx1Z5X72UZ0TrZNG0N7zt8yZjO/7uNSPWVrjkHUQNdkXK4s2qfOKBjPPiywczA+thiuT0J6+nJmgsgdmEqA/x1wOnAriTA3qQhHM9YZya8hJ9eAeDp0/hGkVKxsun7KHX6iNArDM13R2pLI2GjedXep5qwXT6z/RecoxZjdK5cA9OG/2R4FfmCdSFZ+t7MD1i5Xb6FqNOK2VPhWLWk/CwphOlH3VoArL272QkpiJFUSGaAfebttSnrsb9HwzVZsM5fEb4L+gLdYt+fLWtxWx+0NfKHfJzw==
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=ZuWZ8w4oPGI2Wbx9ctlwKjAwIeW0NZ1TQKXIvzYxzbo=; b=sV3Zl2QjlR6y8lC5AjvTYtbedYnavdgzmWJGNCDFF3IdOr6ppUJwwp2e4winXBggb83vnlI/wr/kdDqIdvZwY+h/PNG9xZkmKak+a8i8m3AifcLCH8iiNe/S/XxngZSceeXzjVj4pgQHUE/f/ALmxDc2Cb5c9JPZT/fU3vEyhSk=
Received: from BN7PR11MB2594.namprd11.prod.outlook.com (52.135.246.159) by BN7PR11MB2691.namprd11.prod.outlook.com (52.135.245.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.14; Mon, 9 Dec 2019 13:32:44 +0000
Received: from BN7PR11MB2594.namprd11.prod.outlook.com ([fe80::c72:fa12:757e:cca3]) by BN7PR11MB2594.namprd11.prod.outlook.com ([fe80::c72:fa12:757e:cca3%5]) with mapi id 15.20.2516.014; Mon, 9 Dec 2019 13:32:44 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, 6man <6man@ietf.org>
Subject: Re: Extension Header Insertion
Thread-Topic: Extension Header Insertion
Thread-Index: AdWuPVK+SdXEObEXRIuXhLVkiNme8QAV6u5g
Date: Mon, 09 Dec 2019 13:32:44 +0000
Message-ID: <BN7PR11MB2594C659834223AB3503B548C8580@BN7PR11MB2594.namprd11.prod.outlook.com>
References: <BN7PR05MB5699D9BA988F96E2F41CD390AE580@BN7PR05MB5699.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB5699D9BA988F96E2F41CD390AE580@BN7PR05MB5699.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-12-09T03:04:25.8790012Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=11; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Unknown
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ddukes@cisco.com;
x-originating-ip: [2605:8d80:501:2dd0:e571:1db1:d31f:ef29]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 71f6e338-a68b-4086-85a1-08d77cac4610
x-ms-traffictypediagnostic: BN7PR11MB2691:
x-microsoft-antispam-prvs: <BN7PR11MB26917F6ADB05663E4FDCC3B4C8580@BN7PR11MB2691.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 02462830BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(136003)(396003)(39860400002)(376002)(189003)(199004)(5660300002)(86362001)(81156014)(66946007)(66476007)(66556008)(81166006)(66446008)(55016002)(64756008)(8676002)(71190400001)(316002)(71200400001)(4743002)(3480700005)(53546011)(6506007)(8936002)(7116003)(110136005)(33656002)(4744005)(76116006)(478600001)(9686003)(7696005)(186003)(2906002)(229853002)(52536014); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR11MB2691; H:BN7PR11MB2594.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Tz/L1nJOQLOufqYZgZDVTpKBaRb2E1mZK6h/yO5R4gLRyGOnuWBLuoYsmExz+VsM2MEiYlkr4mbttm/3zR7f3Lfca8RTgrUuFLf/S2l/d5JTMjIvFee5n2wlxoHRI4m2x6Rmwm+lQXWflBI872S+Ykp3ZBN6+rgyVDOCq0gxsPDWpN4yFeOG/9fV0GHfJbOcx6NYBOw+Vnbxhv2MfrciUlFX3asIZaCLbAPqpZ6tX3ixDvvmW7G/R5tIoSxrBAgCrcCk5y5y/e+W6wYLrZfnWhndUBo24D1h10o9QPPcFFz5fjWcb9PuNE+oxsLUWD5i5GcEO0FPV8CJuQSFuAxIamQBPl9baZR+9UOEVOV32XxXJKv/ZCbNlrpuJEqN79DpDjzmE3lM8QFX1EPjRsu/CcRu8fZSiqq2tevZNZh5kIC1NrhSVJBAzCDE8mtJbj9v
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN7PR11MB2594C659834223AB3503B548C8580BN7PR11MB2594namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 71f6e338-a68b-4086-85a1-08d77cac4610
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Dec 2019 13:32:44.5383 (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: vYacS7REcLQBk+2bSqBtn65KZWWiZAXLBL7amAcWRYfIpt9ZDArY7DADEKz0Q/NXyHydTWdg7kGpJ1elOW6w8A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2691
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/JtaJ9BbA8KZK05FHYZhXcHPU12A>
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, 09 Dec 2019 13:32:51 -0000

Hi Ron.

Yes, this is possible with SRH insertion.

Darren

________________________________
From: ipv6 <ipv6-bounces@ietf.org> on behalf of Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
Sent: Sunday, December 8, 2019 10:04 PM
To: 6man
Subject: Extension Header Insertion

Folks,

This question is posed primarily to the proponents of Extension Header insertion.

Do you think that it is acceptable to insert a second routing header into a packet that already has one, so the resulting packet looks like the following:


  *   IPv6 header
  *   SRH
  *   SRH
  *   Upper-layer header

Would this be common in TI-LFA?

                                                                      Ron



Juniper Business Use Only

v2.23.0 | Report a Bug | By Email