Re: Extension Header Insertion
"Darren Dukes (ddukes)" <ddukes@cisco.com> Mon, 09 December 2019 13:31 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 40F6E120089 for <ipv6@ietfa.amsl.com>; Mon, 9 Dec 2019 05:31:34 -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=BSjIbrEn; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=cYvyZ8JW
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 rVX3pI1x80r3 for <ipv6@ietfa.amsl.com>; Mon, 9 Dec 2019 05:31:31 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0B4712007A for <6man@ietf.org>; Mon, 9 Dec 2019 05:31:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10978; q=dns/txt; s=iport; t=1575898291; x=1577107891; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=imFYEMAJ2qXeaIkgj1WGrL7aLenOqrXFzHl47A8syu4=; b=BSjIbrEn4tlaGStjxt61ItMG+UdxyJHmLETVx5h6EihxofUtP38iHlrQ FmNMQt9R6t+HSi+zKrviYaRZPakCwlnwRzdz0lNQOIaBsPeN6QIbcpP+b on07ZqpdbHvpXO+8pIE3qpyR0L9g+9M7kQ1SfkHhJMtlYmffTC/sShLpz s=;
IronPort-PHdr: 9a23:OVHNyBwhRtA8/GfXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuJBVD4IeXCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DADAArTO5d/4MNJK1kHAEBAQEBBwEBEQEEBAEBgX6BHC8pJwV6SiAECyqHSAOLA06CEZMjhGKBQoEQA1QJAQEBDAEBLQIBAYRAAoIZJDgTAgMNAQEEAQEBAgEFBG2FNwyFUgEBAQEDEi4BATgPAgEIEQQBAS8yHQgBAQQBEggahHpNAy4BAqAdAoE4iGGCJ4J+AQEFhQ8YghcJgTaMGBqBQT+BWIJMPoQxGoNAgiyNL4hIgkCHEI8WCoIujEyJNYJCl3COSoFFmGYCBAIEBQIOAQEFgWkigVhwFYMnUBEUjGaBJwEIgkOKU3SBKI1pAQE
X-IronPort-AV: E=Sophos;i="5.69,294,1571702400"; d="scan'208,217";a="379303959"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Dec 2019 13:31:30 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id xB9DVUXT026515 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Dec 2019 13:31:30 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Dec 2019 07:31:30 -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:31:29 -0600
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.1473.3 via Frontend Transport; Mon, 9 Dec 2019 07:31:29 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bSFTlNxKvMw7llhUECBOT/mwug3x/rms43lzTBGHtyrl0YDx6Tb6gyeKlDOQOZJsu1QpXaChyJCDS6BlrKcFgNIzfppVkCwua/OCyPfC6AWz+fAlp91ovyMxHPpktrDa7b60/6KKgQEmvfE2pGIzRYECO5I+RZAoZeWtpGvpWS2Wmcx2zoKmcupZT8/Zuh/NHfbnArzwsT4ECUPLD/L/5s+54i76sH1Li+NpZrOjdbf0KQhZn1Itfj0SucyQhNt604EM/5h34FDFWaWK6aZJuXia2zlHz5cphuVQA+Q4yg9YB9dMNCNKT8gdE7Yx3eCCJGU2M6OLf1YiJjZunjOGNw==
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=rHXZCM9zllRv2Whj9NeATIzexASFwipYEqAgmFxxNX0=; b=O0pzeb207oPoZzrujrlrK9OTUAh4YLwPgBuLkO41p6GPo1kCiSn4p8LaCSWS+OS9oEvaAToA3VQA1s2UlAhiQDmBbr5g1gqJJZ9q4iAIdfbbZXYHXFi7cPrwuj2vwqNFONIfhI5UeJgNJ4X/XRx5fR0qtpPJHCyzCfjw67ESgax+3XYBblI6jy8K33qrG3DdRv1vc87wr8YFVYqs8vo2jJSTGk75uy3ultVnYjWzaOPpieQARvoXTisDhHKh3CInv7t4VcsoOZE4QdEluDU1TpGg4JV7kYNZItclY5Cb4txVvCFccy3cxCzDi9ve8/5udn5KPZ5JKSNC4vhtoxUmnw==
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=rHXZCM9zllRv2Whj9NeATIzexASFwipYEqAgmFxxNX0=; b=cYvyZ8JWsDbqUJtin5bCAUy5YaTcLNOZWUyp/CMUmM9fJYKA9O9KD8+3uwHCoprJxosssj0Ek0Ft/KGRaTtAd6nK3CVsgZ1oc+UVqZ65bqgEEW3tFPaARSNYnu+t9++HasuJBIHXZG0NEMfXs94KsxOoKeXLDFUUhC1qXUmXoos=
Received: from BN7PR11MB2594.namprd11.prod.outlook.com (52.135.246.159) by BN7PR11MB2851.namprd11.prod.outlook.com (52.135.254.28) 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:31:28 +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:31:28 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, '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+SdXEObEXRIuXhLVkiNme8QANm90AAAgdLQA=
Date: Mon, 09 Dec 2019 13:31:28 +0000
Message-ID: <BN7PR11MB25946B6A525A7D74B2479F17C8580@BN7PR11MB2594.namprd11.prod.outlook.com>
References: <BN7PR05MB5699D9BA988F96E2F41CD390AE580@BN7PR05MB5699.namprd05.prod.outlook.com>, <00dc01d5ae73$c361b450$4a251cf0$@olddog.co.uk>
In-Reply-To: <00dc01d5ae73$c361b450$4a251cf0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
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: 61443f37-ad69-45e1-ef29-08d77cac18d5
x-ms-traffictypediagnostic: BN7PR11MB2851:
x-microsoft-antispam-prvs: <BN7PR11MB28518E8A350E5029AF626582C8580@BN7PR11MB2851.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 02462830BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(39860400002)(376002)(136003)(346002)(199004)(189003)(110136005)(81156014)(81166006)(8936002)(8676002)(316002)(53546011)(6506007)(7696005)(71190400001)(71200400001)(66446008)(5660300002)(3480700005)(52536014)(66556008)(64756008)(66476007)(66946007)(4743002)(33656002)(9686003)(478600001)(55016002)(2906002)(186003)(7116003)(86362001)(76116006)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR11MB2851; H:BN7PR11MB2594.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: np9I79SHX7nXlQDEMkB3W00ITxmWkcW78UjQAz4HBultgnyXecRO3Apq8h3lA8u+mvL0RkMVIm371M/DfsNIpvCPDDtfZgqpJy31omZQ6tshkNFXhJ4Us7tZnpYANQVrQMgBlIPW3wCAo6qEMJZdXL1atImk/FO/CcF47hs31teuL5m2ky9mQr9rdrhE7GXaxLnIMdIhA0GdwjbPh8lsIT28zygkf4/cAlMFF5oJI2qDNQ4BYFxWS4dNJDe6HIup9vgcH60oVzwKKpQ2/FTNobdfpgpi/dJ4Nb3YpjLSJibb5ffNfANHyJMXDZNEyjMum1MJHWqpHSUEbsMtFLu7tXej+sT7ANewPidXGjaRaclo7gLYBHeprmvTXVPN8sc6025jrliqRNNt4PPhbm9NunMaFhZdP3SXW94r8k8ZhF0QYLUC/+nbH5Ia2qqSbbSG
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN7PR11MB25946B6A525A7D74B2479F17C8580BN7PR11MB2594namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 61443f37-ad69-45e1-ef29-08d77cac18d5
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Dec 2019 13:31:28.7058 (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: iO7TGJIFVhXvoJDHZ5+YrMbJlAlW9caRm8fZdb4NIveA2QM9J1N5Kfme5oSsafeWFDdOltWXtIqr8IDSNY9M/w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2851
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SOOPhwJ49TBzSIWSdG3av7HAFCU>
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:31:34 -0000
Hi Adrian. You failed to quote the section of rfc 8200 where it says “IPv6 nodes must accept and attempt to process extension headers in any order and occurring any number of times in the same packet,” I do not agree with your assumptions nor the attempt to imply something about the Other drafts. Darren. ________________________________ From: ipv6 <ipv6-bounces@ietf.org> on behalf of Adrian Farrel <adrian@olddog.co.uk> Sent: Monday, December 9, 2019 4:34 AM To: 'Ron Bonica'; '6man' Subject: RE: Extension Header Insertion Hi Ron, I think we can jump to a quick answer on this because draft-ietf-spring-srv6-network-programming-05 says: We assume that the SRH may be present multiple times inside each packet. Thus we may assume that the proponents of Extension Header insertion do think that it is acceptable to insert a second routing header into a packet that already has one. And 8200 is clear when it says: Each extension header should occur at most once, except for the Destination Options header, which should occur at most twice (once before a Routing header and once before the upper-layer header). So draft-ietf-spring-srv6-network-programming-05 includes a false assumption which need to be either removed or secured through an update to 8200. Ideally, I suppose, draft-ietf-6man-segment-routing-header would have contained the clarification that the SRH could be present multiple times (updating 8200 as it went). Cheers, Adrian From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Ron Bonica Sent: 09 December 2019 03:04 To: 6man <6man@ietf.org> 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
- Extension Header Insertion Ron Bonica
- RE: Extension Header Insertion Adrian Farrel
- Re: Extension Header Insertion Darren Dukes (ddukes)
- Re: Extension Header Insertion Darren Dukes (ddukes)
- Re: Extension Header Insertion Tom Herbert
- RE: Extension Header Insertion Adrian Farrel
- Re: Extension Header Insertion Gyan Mishra
- RE: Extension Header Insertion Ron Bonica
- Re: Extension Header Insertion Brian E Carpenter
- What if? [was Re: Extension Header Insertion] Brian E Carpenter
- Re: What if? [was Re: Extension Header Insertion] Gyan Mishra
- Re: What if? [was Re: Extension Header Insertion] Gyan Mishra
- Re: What if? [was Re: Extension Header Insertion] Fernando Gont
- Re: What if? [was Re: Extension Header Insertion] Fernando Gont
- Re: What if? [was Re: Extension Header Insertion] Fernando Gont
- Re: Extension Header Insertion Stewart Bryant
- Re: What if? [was Re: Extension Header Insertion] Brian E Carpenter
- Re: What if? [was Re: Extension Header Insertion] Gyan Mishra
- RE: Extension Header Insertion Ron Bonica
- RE: What if? [was Re: Extension Header Insertion] Ron Bonica
- Re: What if? [was Re: Extension Header Insertion] Darren Dukes (ddukes)
- Re: What if? [was Re: Extension Header Insertion] Fernando Gont
- Re: What if? [was Re: Extension Header Insertion] Fernando Gont
- Re: Extension Header Insertion Fernando Gont
- Re: What if? [was Re: Extension Header Insertion] Brian E Carpenter
- Re: What if? [was Re: Extension Header Insertion] Warren Kumari
- Re: What if? [was Re: Extension Header Insertion] Fernando Gont
- Re: What if? [was Re: Extension Header Insertion] Fernando Gont
- Re: What if? [was Re: Extension Header Insertion] Gyan Mishra
- Re: What if? [was Re: Extension Header Insertion] Stewart Bryant
- Re: What if? [was Re: Extension Header Insertion] Jeff Tantsura
- Re: What if? [was Re: Extension Header Insertion] Brian E Carpenter
- Re: What if? [was Re: Extension Header Insertion] Gyan Mishra
- Re: What if? [was Re: Extension Header Insertion] Gyan Mishra
- Re: What if? [was Re: Extension Header Insertion] Jeff Tantsura
- Re: What if? [was Re: Extension Header Insertion] Gyan Mishra
- Re: What if? [was Re: Extension Header Insertion] Stewart Bryant