RE: Compressed Routing Header idea
"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 22 May 2020 17:18 UTC
Return-Path: <Fred.L.Templin@boeing.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 4B9DA3A0C4E; Fri, 22 May 2020 10:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.com
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 Cwb-ZHmIHqW3; Fri, 22 May 2020 10:18:48 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 D6FAF3A0CB7; Fri, 22 May 2020 10:18:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 04MHIh6Z005179; Fri, 22 May 2020 13:18:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1590167926; bh=OV+4AOr/QeTLHRmle2DojNcfvPtBafdJ1r5GEij6pXo=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=ptkgBO+doaTy4uAckzXRPLXy4jWpoNgGguFdTJlrp7knLJICqUbZUT+doM8uJfoTm rv5Als9fS+gQn9ZxVekuJlwjdzsMx0As+7SezqtyRQQ50BeERkgk+LUOcCI5EKY2/4 MLJf8Q3MbEF4PYteusn4tZZA3+N/KoQI1IvHV2pLfHqsFUtKXrBs9kjVKPATTN6huW xgBSS/fDVZ1qv0ggosFmrubLxuc9QJmX/Uyfe9+RhUvA2R+ajHaE/MRUdAmP6BZdGC 5OJphNMkLZJTX7B1V1XfcFt9f6jB5TgjniVJISIZZlahuLyZTkQGJxzLeIvKjjBiRL Q+JvQtMuibdxg==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 04MHIXOa003580 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 22 May 2020 13:18:33 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1979.3; Fri, 22 May 2020 10:18:31 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1979.003; Fri, 22 May 2020 10:18:31 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ron Bonica <rbonica@juniper.net>, Gyan Mishra <hayabusagsm@gmail.com>, 6MAN <6man@ietf.org>
CC: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: Compressed Routing Header idea
Thread-Topic: Compressed Routing Header idea
Thread-Index: AdYtHG+8rC3YEibIRJu4gVbarLwgbQABz5wgAACO2SAACDa1AACY5l8AAAUxy2AAAIBvAAAGecGAAAInygAAAQKqQAAdIGsQ
Date: Fri, 22 May 2020 17:18:31 +0000
Message-ID: <d076057cf8574d92bd1c461a81afc7c9@boeing.com>
References: <2a844eb431b346b8931196c5e21d33ae@boeing.com> <MN2PR11MB35654AC2F2C85717097DA6C6D8B80@MN2PR11MB3565.namprd11.prod.outlook.com> <e3c8e3a6e80047cd9033e48997e0bb99@boeing.com> <CABNhwV2RCii_e6H1L2BgoyqjzGOOWf6+=CN_KJc+KmH9eYZRgw@mail.gmail.com> <4af522c96b53457781e428432543e592@boeing.com> <DM6PR05MB6348D50CEDC3E2D502E943C6AEB70@DM6PR05MB6348.namprd05.prod.outlook.com> <8441ee4d-f5af-c6ac-53f3-10ef7804d201@gmail.com> <2fda98050af044ae9738f12f1d62ee73@boeing.com> <e9430724-d4f0-d74c-039c-e51f4aabc75a@gmail.com> <MW3PR11MB4570862D5D3E6BE1CD66811DC1B40@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4570862D5D3E6BE1CD66811DC1B40@MW3PR11MB4570.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 49A6BE0760676AC8655018C77751CF3B461288B82171830880E8A0A3DA2AFFF72000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/OImj08WtchZBo1y0mNmgqOnFsV4>
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: Fri, 22 May 2020 17:18:59 -0000
Ketan, I did just a very quick search on the docs you provided and did not see anything about RFC2473 encapsulation as a "mid-layer" encapsulation as I am doing in the AERO spec. It is this mid-layer encapsulation where I want to insert and delete a special-purpose RH that makes the final transition to the ultimate destination. You can probably find more details in my previous replies to Tom, Ron and Brian. Thanks - Fred > -----Original Message----- > From: Ketan Talaulikar (ketant) [mailto:ketant@cisco.com] > Sent: Thursday, May 21, 2020 8:25 PM > To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Templin (US), Fred L <Fred.L.Templin@boeing.com>; Ron Bonica > <rbonica@juniper.net>; Gyan Mishra <hayabusagsm@gmail.com>; 6MAN <6man@ietf.org> > Cc: Pascal Thubert (pthubert) <pthubert@cisco.com>; IPv6 List <ipv6@ietf.org> > Subject: RE: Compressed Routing Header idea > > Hi Fred, > > I agree with what Brian says. > > You may be able to get some context from https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-15#section-4.16.1 > but perhaps may not be the complete one since the SRv6 solution might not be something that could be understood by that one > specific section alone. I would suggest to reach out to the authors of that document for details. > > FWIW, the PSP solution has actually already been deployed in several production networks and supported by multiple vendors [1]. > > Unrelated to your specific question but might be applicable to your use-case as well - please also check out the proposal for insertion > [2] which is again also implemented and deployed [1]. > > The SRH proposal does indeed expand the boundaries and application of IPv6 ... and unfortunately that does seem to make it's > proponents seem like "bad persons" to some in the WG. > > Thanks, > Ketan > > [1] https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/ > [2] https://datatracker.ietf.org/doc/draft-voyer-6man-extension-header-insertion/ > > > -----Original Message----- > From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Brian E Carpenter > Sent: 22 May 2020 08:20 > To: Templin (US), Fred L <Fred.L.Templin@boeing.com>; Ron Bonica <rbonica@juniper.net>; Gyan Mishra > <hayabusagsm@gmail.com>; 6MAN <6man@ietf.org> > Cc: Pascal Thubert (pthubert) <pthubert@cisco.com>; IPv6 List <ipv6@ietf.org> > Subject: Re: Compressed Routing Header idea > > On 22-May-20 13:48, Templin (US), Fred L wrote: > > Brian, yes I think it would require ignoring some "SHOULD/MUST NOT" or > > something in RFC8200. Would that make me a bad person if I were to do that? > > Well, I assume you have read all the threads about "penultimate segment pop", which is exactly the same thing in SRH-land, and draft- > bonica-6man-ext-hdr-update. > > > Or, to be true to the community I suppose the right thing to do would > > be to properly update the normative references to cite the exception. > > Do you know if anyone has already tried to do that? > > https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-15#section-4.16.1 says: > > "This behavior does not contravene Section 4 of [RFC8200] because the > current destination address of the incoming packet is the address of > the node executing the PSP behavior." > > But not everybody agrees with that, and there's already one appeal to the IESG in progress. > > None of which makes you a bad person, of course. But it would presumably be just as controversial in your draft as it is in the Spring > draft. > > Regards > Brian > > > Thanks - Fred > > > >> -----Original Message----- > >> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] > >> Sent: Thursday, May 21, 2020 3:43 PM > >> To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; Templin (US), > >> Fred L <Fred.L.Templin@boeing.com>; Gyan Mishra > >> <hayabusagsm@gmail.com>; 6MAN <6man@ietf.org> > >> Cc: Pascal Thubert (pthubert) <pthubert@cisco.com>; IPv6 List > >> <ipv6@ietf.org> > >> Subject: Re: Compressed Routing Header idea > >> > >> On 22-May-20 10:33, Ron Bonica wrote: > >>> Fred, > >>> > >>> > >>> > >>> When a node decrements Segments Left to 0, it causes all subsequent > >>> nodes to ignore the Routing header. So, I don’t see a good > >> reason to remove the Routing header. It will be ignored by all downstream nodes anyway. > >> > >> Yes, quite apart from the disputed breach of RFC8200. > >> > >> Brian > >> > >>> > >>> > >>> > >>> Ron > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> Juniper Business Use Only > >>> > >>> *From:*Templin (US), Fred L <Fred.L.Templin@boeing.com> > >>> *Sent:* Thursday, May 21, 2020 4:00 PM > >>> *To:* Gyan Mishra <hayabusagsm@gmail.com>; 6MAN <6man@ietf.org>; Ron > >>> Bonica <rbonica@juniper.net> > >>> *Cc:* IPv6 List <ipv6@ietf.org>; Pascal Thubert (pthubert) > >>> <pthubert@cisco.com> > >>> *Subject:* RE: Compressed Routing Header idea > >>> > >>> > >>> > >>> *[External Email. Be cautious of content]* > >>> > >>> > >>> > >>> Hi, just seeing this question now (below). The idea is that the > >>> router that processes > >>> > >>> the penultimate SID would “pair” it with the ultimate SID so that > >>> the penultimate SID > >>> > >>> is written as the final IPv6 destination while the ultimate SID > >>> (which may include an > >>> > >>> address and port number) is used as a destination for IPv6-in-IP > >>> encapsulation. So, > >>> > >>> the final hop router before the final destination would be the one to extract it. > >>> > >>> > >>> > >>> I had a somewhat related question – can the final hop router before > >>> the final > >>> > >>> destination delete the Routing Header before forwarding? > >>> > >>> > >>> > >>> Thanks - Fred > >>> > >>> > >>> > >>> Fred > >>> > >>> > >>> > >>> Curious what would be the particular application use case for > >>> variable compressed routing header to add ancillary info like port > >>> or > >> other miscellaneous info. > >>> > >>> > >>> > >>> I am guessing the final destination would have to extract the > >>> ancillary. In a connection the tcp or udp source is the same unless > >> using RPC or an app using dynamic port allocation and want to save the port info somewhere else. > >>> > >>> > >>> > >>> https://datatracker.ietf.org/doc/draft-templin-6man-crh-variable/ > >> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-te > >> mplin-6man-crh-variable/__;!!NEt6yMaO- > >> gk!ViLHxbEJqhubTR_jBFZ9qv59Xn3jPyPGQcTN33jDxZuo2nzpBinDu4TXl9lvoN3y$> > >>> > >>> > >>> > >>> > >>> > >>> Thanks > >>> > >>> > >>> > >>> Gyan > >>> > >>> > >>> > >>> On Mon, May 18, 2020 at 11:12 AM Templin (US), Fred L > >>> <Fred.L.Templin@boeing.com <mailto:Fred.L.Templin@boeing.com>> > >> wrote: > >>> > >>> Pascal, thanks I did not know about this but at first glance I do not believe RFC8138 fully > >>> satisfies what I need. First, I want to be able to support both left-side (most significant > >>> bits) and right-side (least significant bits) compression. Second, I want to be able to > >>> compress to the byte granularity for any length from 0 to 16 bytes. And, third, I want > >>> to be able to include an ancillary piece of information (e.g., an application port number) > >>> with each IPv6 address. So, I submitted a short draft showing the format that I would > >>> see as being flexible to support my use case and I think perhaps many other: > >>> > >>> > >>> https://datatracker.ietf.org/doc/draft-templin-6man-crh-variable/ > >> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-te > >> mplin-6man-crh-variable/__;!!NEt6yMaO- > >> gk!ViLHxbEJqhubTR_jBFZ9qv59Xn3jPyPGQcTN33jDxZuo2nzpBinDu4TXl9lvoN3y$> > >>> > >>> I did include a reference to RFC8138 - let me know your thoughts. > >>> > >>> Fred > >>> > >>> > -----Original Message----- > >>> > From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com <mailto:pthubert@cisco.com>] > >>> > Sent: Monday, May 18, 2020 7:55 AM > >>> > To: Templin (US), Fred L <Fred.L.Templin@boeing.com > >>> <mailto:Fred.L.Templin@boeing.com>>; IPv6 List <ipv6@ietf.org > >> <mailto:ipv6@ietf.org>> > >>> > Subject: RE: Compressed Routing Header idea > >>> > > >>> > Hello Fred: > >>> > > >>> > Are you aware of RFC 8138? See > >>> https://tools.ietf.org/html/rfc8138#section-5.1 > >> <https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc8138*secti > >> on-5.1__;Iw!!NEt6yMaO- > >> gk!ViLHxbEJqhubTR_jBFZ9qv59Xn3jPyPGQcTN33jDxZuo2nzpBinDu4TXl0b3-Gbz$> > >>> > The addresses in the source route header can be compressed as follows: > >>> > > >>> > " > >>> > > >>> > +-----------+----------------------+ > >>> > | 6LoRH | Length of compressed | > >>> > | Type | IPv6 address (bytes) | > >>> > +-----------+----------------------+ > >>> > | 0 | 1 | > >>> > | 1 | 2 | > >>> > | 2 | 4 | > >>> > | 3 | 8 | > >>> > | 4 | 16 | > >>> > +-----------+----------------------+ > >>> > > >>> > Figure 7: The SRH-6LoRH Types > >>> > > >>> > " > >>> > You need multiple SRH-6loRH if you have different sizes to accommodate.. > >>> > > >>> > Keep safe > >>> > > >>> > Pascal > >>> > > >>> > > -----Original Message----- > >>> > > From: ipv6 <ipv6-bounces@ietf.org <mailto:ipv6-bounces@ietf.org>> On Behalf Of Templin (US), Fred L > >>> > > Sent: lundi 18 mai 2020 16:04 > >>> > > To: IPv6 List <ipv6@ietf.org <mailto:ipv6@ietf.org>> > >>> > > Subject: Compressed Routing Header idea > >>> > > > >>> > > Hi, I have a use case where some IPv6 addresses that would go into a routing > >>> > > header are more compressible than others and so I am wondering if some kind > >>> > > of "hybrid" compressed routing header would be possible.. For example, if one > >>> > > address can be compressed down to > >>> > > 16 bits, then include only those 16 bits; if a different address can only be > >>> > > compressed down to 32 bits, then include the 32 bits; if yet a different address > >>> > > cannot be compressed at all, then include all 128 bits. And, there may be many > >>> > > more sizes in between. > >>> > > > >>> > > RFC4191 Section 2.3 shows an example of how an IPv6 prefix/address can be > >>> > > compressed to a variable length. Essentially, a length byte followed by a > >>> > > variable-length prefix. That way there would still be "pretty good compression" > >>> > > albeit with an extra byte per prefix. And, it would be a generalized form that > >>> > > would only require a single routing header type value. > >>> > > How would it be if we did something like that? > >>> > > > >>> > > Fred > >>> > > > >>> > > > >>> > > > >>> > > -------------------------------------------------------------------- > >>> > > IETF IPv6 working group mailing list > >>> > > ipv6@ietf.org <mailto:ipv6@ietf.org> > >>> > > Administrative Requests: > >>> https://www.ietf.org/mailman/listinfo/ipv6 > >> <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/ipv > >> 6__;!!NEt6yMaO- > >> gk!ViLHxbEJqhubTR_jBFZ9qv59Xn3jPyPGQcTN33jDxZuo2nzpBinDu4TXl0Q2OkFT$> > >>> > > > >>> -------------------------------------------------------------------- > >>> > >>> -------------------------------------------------------------------- > >>> IETF IPv6 working group mailing list > >>> ipv6@ietf.org <mailto:ipv6@ietf.org> > >>> Administrative Requests: > >>> https://www.ietf.org/mailman/listinfo/ipv6 > >> <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/ipv > >> 6__;!!NEt6yMaO- > >> gk!ViLHxbEJqhubTR_jBFZ9qv59Xn3jPyPGQcTN33jDxZuo2nzpBinDu4TXl0Q2OkFT$> > >>> > >>> -------------------------------------------------------------------- > >>> > >>> -- > >>> > >>> 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> > >>> > >>> > >>> > >>> > >>> > >>> > >>> -------------------------------------------------------------------- > >>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative > >>> Requests: https://www.ietf.org/mailman/listinfo/ipv6 > >>> -------------------------------------------------------------------- > >>> > > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > --------------------------------------------------------------------
- RE: Compressed Routing Header idea Ketan Talaulikar (ketant)
- Re: Compressed Routing Header idea Brian E Carpenter
- RE: Compressed Routing Header idea Ron Bonica
- Re: Compressed Routing Header idea Tom Herbert
- RE: Compressed Routing Header idea Templin (US), Fred L
- RE: Compressed Routing Header idea Templin (US), Fred L
- RE: Compressed Routing Header idea Pascal Thubert (pthubert)
- Compressed Routing Header idea Templin (US), Fred L
- RE: Compressed Routing Header idea Templin (US), Fred L
- Re: Compressed Routing Header idea Gyan Mishra
- RE: Compressed Routing Header idea Chengli (Cheng Li)
- RE: Compressed Routing Header idea Templin (US), Fred L
- RE: Compressed Routing Header idea Ron Bonica
- Re: Compressed Routing Header idea Brian E Carpenter
- RE: Compressed Routing Header idea Templin (US), Fred L
- Re: Compressed Routing Header idea Gyan Mishra
- RE: Compressed Routing Header idea Templin (US), Fred L
- RE: Compressed Routing Header idea Templin (US), Fred L
- RE: Compressed Routing Header idea Templin (US), Fred L