RE: Extension Header Insertion

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 09 December 2019 15:33 UTC

Return-Path: <adrian@olddog.co.uk>
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 62D6D120099 for <ipv6@ietfa.amsl.com>; Mon, 9 Dec 2019 07:33:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.737
X-Spam-Level:
X-Spam-Status: No, score=-2.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.14, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 4pvlrt_TvoHi for <ipv6@ietfa.amsl.com>; Mon, 9 Dec 2019 07:33:13 -0800 (PST)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2540712000F for <6man@ietf.org>; Mon, 9 Dec 2019 07:33:12 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id xB9FX7Ge031206; Mon, 9 Dec 2019 15:33:07 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 43DC622044; Mon, 9 Dec 2019 15:33:07 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS id 3815022042; Mon, 9 Dec 2019 15:33:07 +0000 (GMT)
Received: from LAPTOPK7AS653V ([84.93.96.25]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id xB9FX3PB031813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 9 Dec 2019 15:33:06 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Darren Dukes (ddukes)'" <ddukes@cisco.com>, '6man' <6man@ietf.org>
References: <BN7PR05MB5699D9BA988F96E2F41CD390AE580@BN7PR05MB5699.namprd05.prod.outlook.com>, <00dc01d5ae73$c361b450$4a251cf0$@olddog.co.uk> <BN7PR11MB25946B6A525A7D74B2479F17C8580@BN7PR11MB2594.namprd11.prod.outlook.com>
In-Reply-To: <BN7PR11MB25946B6A525A7D74B2479F17C8580@BN7PR11MB2594.namprd11.prod.outlook.com>
Subject: RE: Extension Header Insertion
Date: Mon, 09 Dec 2019 15:33:00 -0000
Organization: Old Dog Consulting
Message-ID: <01c401d5aea5$f3b0ba20$db122e60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C5_01D5AEA5.F3B1A480"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI439AHKnUbCBQmWia4zMPSIdSA4QFeqsHJARNZ7k6m1+gX0A==
Content-Language: en-gb
X-Originating-IP: 84.93.96.25
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25094.000
X-TM-AS-Result: No--14.673-10.0-31-10
X-imss-scan-details: No--14.673-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25094.000
X-TMASE-Result: 10--14.673400-10.000000
X-TMASE-MatchedRID: CxmI61mtwh9xWR+9hcFWA3FPUrVDm6jtekMgTOQbVFuZt08TfNy6OKOI rKL+ynQkpECMsom1kW7mlkilUx8QrL7NV4PnjfmaPEoSfSIsZrvyCvICuK46cmer6T5jkOGAkDv MD44L9H3HAZ6r35f1N9TjNmIVu36fnoIpphgZ80YK4MBRf7I7puRswBJPCCuIRJts9OIxqBPIQM Uy4ToeqKPElFqGhlJnSCvALEZrRJ2VzExQz+f3kX+ffPip7DDoXWNxd7+7vSjbw6NvULhmF26Kq EKoSkaftqy4fGtVdQpwwx7fe7FfbDzr4TJKjukKWTGejGdB9VIbQ57RP6lOUfAlhlr8vzcdSxzl MEEmixO3xrgEs5sr4a+SjKc1P0nEPz62uxDLhUy6iJsmkdGsWQZyESFXAljfwHCsHrMIcfAHLJW KaOYkk7I86eWviFmuuEEbrtBsW0823LDAh/mSxUhft0m/UEjou8ZgmQ167rXtX9Gt3sULEma3gp b4oyKece8sW0Q2hmG023N+wvUXQOXGQXIAp7mW71Wx2uUbPLdDr8MVm6DK3bv81BNUjUj5zEVDG nc+EfKahG/i8Ja1Y7dYFVfIRaXSnMOyXYlQyp+soC9I+K53IeqhuTPUDQDtzcoP6tZuq3FJPus6 r/YfultyNHRhmjtfAllRMNbKfG3a8AiR/nR5g8KVNVkgZd/IHiG5YR9Ep+kXM2Z1UyweuO/JKo6 3i0vVLPtrQd14tHvtrTvo40oHfs2GnNBwQqk9HPYwOJi6PLkwQTzTIFJCzpGYGmQ9yE9VlwAF8D AEzOTRv+j60AlkulE9Y9nltHKELDC3FGTHI3eeAiCmPx4NwGmRqNBHmBvevqq8s2MNhPDPPeN6H N6d7M+9+OQ9U/5f33fj+sMArfNSleqDFXU3qWXagc3KfUKSHaPNLjEl51hrzmLRBlOMhIgewuuT qrDGQ8mNR1SjAmz+fo+Sh+WVpNDqi8urj73JHJ/Q9ZUwBeT/sHNxMwstXw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/10FgoPKWe4tcnChbLVOw8mwx7pA>
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 15:33:16 -0000

Hello Darren,

 

Thanks for your considered and friendly reply.

 

Thanks for the additional pointer to 8200. I (of course) was not involved in
the production of that document, but I read it as doing two things:

1.	Setting the high-level behaviour for general processing.
This is the text you quote.
2.	Giving detailed rules about specific EHs for order and presence.
The text I quoted.

 

So I would be guided by 8200 to not expect to see a second routing header
(e.g., SRH).

 

Of course, I might implement to see the second one and treat it as an
unknown EH. That would be good self-protection code.

 

Now, I said "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 you said "I do not agree with your
assumptions". So can I take it that you do not think it is acceptable to
insert a second SRH into a packet that already has one?

 

Thanks,

Adrian

 

From: Darren Dukes (ddukes) <ddukes@cisco.com> 
Sent: 09 December 2019 13:31
To: adrian@olddog.co.uk; 'Ron Bonica'
<rbonica=40juniper.net@dmarc.ietf.org>; '6man' <6man@ietf.org>
Subject: Re: Extension Header Insertion 

 

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 <mailto:ipv6-bounces@ietf.org> > on behalf
of Adrian Farrel <adrian@olddog.co.uk <mailto: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 <mailto:ipv6-bounces@ietf.org> > On Behalf
Of Ron Bonica
Sent: 09 December 2019 03:04
To: 6man <6man@ietf.org <mailto: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