Re: [Int-area] Using ISO8473 as a network layer to carry flexible addresses

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 03 March 2021 11:06 UTC

IronPort-PHdr: 9a23:TvB1ORKstBySJgzACdmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeGvKk/g1rAXIGd4PVB2KLasKHlDGoH55vJ8HUPa4dFWBJNj8IK1xchD8iIBQyeTrbqYiU2Ed4EWApj+He2YkdQEcf6IVbVpy764TsbAB6qMw1zK6z8EZLTiMLi0ee09tXTbgxEiSD7b6l1KUC9rB7asY8dho4xJw==
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-jia-flex-ip-address-structure@ietf.org" <draft-jia-flex-ip-address-structure@ietf.org>, int-area <int-area@ietf.org>, Toerless Eckert <tte@cs.fau.de>, Jiayihao <jiayihao@huawei.com>, "draft-jia-scenarios-flexible-address-structure@ietf.org" <draft-jia-scenarios-flexible-address-structure@ietf.org>
Thread-Topic: [Int-area] Using ISO8473 as a network layer to carry flexible addresses
Thread-Index: AQHW/f5RvUuomHaoYE6mD4FmcmmPVqpOETQAgCFTIQCAAEziAIABExoAgAF58IA=
Date: Wed, 03 Mar 2021 11:05:42 +0000
Message-ID: <93A96A86-C38A-41D9-867A-CC2FE6999505@cisco.com>
References: <2233700F-9AFF-472B-B3BF-33226339DB6E@gmail.com>
In-Reply-To: <2233700F-9AFF-472B-B3BF-33226339DB6E@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: multipart/alternative; boundary="_000_93A96A86C38A41D9867ACC2FE6999505ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d0d4fc8d-fddf-4bc0-b012-08d8de344949
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2021 11:05:42.1967 (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: tAdgz0gb+d2dVX3Gxdx7bm/0dq6qVtBJg9qza5KlzZU3hC5+eCEGBk06artoaM24xvNmoLvcMoMgyJKG5mjTYQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR11MB5060
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xbe-aln-002.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/ooaHOG0VAYoc14cbXmP0fAiWajo>
Subject: Re: [Int-area] Using ISO8473 as a network layer to carry flexible addresses
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2021 11:06:05 -0000

Hello Stewart, Brian and Toerless:

Interestingly RFC 8138 took one step in that direction. Yes you’re going to need a new Ethertype but it’s still IPv6 I. That is is expressed as a compression not a modification of IPv6.

In the compressed form the header starts with the next hops, the destination and SRH being indiscriminated, the destination is just the first of the list. The size is variable but each hop is at most 128 bits. Because the SRH could encode SRv6 you can already go a long way with this.

If that can help you do what you want, I m happy to explain more...

Keep safe.

Pascal

Le 2 mars 2021 à 13:33, Stewart Bryant <stewart.bryant@gmail.com> a écrit :

On 1 Mar 2021, at 20:08, Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>> wrote:

It would take but a minute to design a longer-address mechanism for IPv6, although I don't have space to include it in the margin of this email**. But it would take many years for it to be widely implemented and deployed, during which time the Internet would be opaque to such addresses.

** Basically, use a prefix such as fb00::/8 to indicate an extended address.

Hi Brian

Basically I think that this fails the backwards compatibility text.

It is perfectly legitimate to write an IPv6 forwarder as follows:

If MACaddress == me and MACtype == IPv6 pass packet to IPv6 forwarder

In IPv6 forwarder:

If version == IPv6 and Hop Limit not exceeded send bytes 24 to 39 to address lookup engine

Wait for address result and forward packet accordingly

Except that this forwarder would have sent a bunch of random junk to the ALE consisting of some of the SA and maybe some of the DA depending on their sizes.

So to stop an old and legitimately designed parser being fooled you really have to use a new MAC type and a new version and as soon as you do that you might as well design the packet optimally for the job at hand.

If the IPv6 designers had followed the strategy of both the Ethernet designers and the ISO8473 designers and put DA before SA then the elegant approach that you and others have proposed at various times would have worked nicely.

Best regards

Stewart

_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area

[Int-area] Using ISO8473 as a network layer to ca… Stewart Bryant
[Int-area] 答复: Using ISO8473 as a network layer t… Jiayihao
Re: [Int-area] Using ISO8473 as a network layer t… Stewart Bryant
Re: [Int-area] Using ISO8473 as a network layer t… Toerless Eckert
Re: [Int-area] Using ISO8473 as a network layer t… Brian E Carpenter
Re: [Int-area] Using ISO8473 as a network layer t… Behcet Sarikaya
Re: [Int-area] Using ISO8473 as a network layer t… Jiayihao
Re: [Int-area] Using ISO8473 as a network layer t… Toerless Eckert
Re: [Int-area] Using ISO8473 as a network layer t… Liguangpeng (Roc, Network Technology Laboratory)
Re: [Int-area] Using ISO8473 as a network layer t… Stewart Bryant
Re: [Int-area] Using ISO8473 as a network layer t… Stewart Bryant
Re: [Int-area] Using ISO8473 as a network layer t… Stewart Bryant
Re: [Int-area] Using ISO8473 as a network layer t… Liguangpeng (Roc, Network Technology Laboratory)
Re: [Int-area] Using ISO8473 as a network layer t… Toerless Eckert
Re: [Int-area] Using ISO8473 as a network layer t… Stewart Bryant
Re: [Int-area] Using ISO8473 as a network layer t… Alexandre Petrescu
Re: [Int-area] Using ISO8473 as a network layer t… Stewart Bryant
Re: [Int-area] Using ISO8473 as a network layer t… Brian E Carpenter
Re: [Int-area] Using ISO8473 as a network layer t… Brian E Carpenter
Re: [Int-area] Using ISO8473 as a network layer t… Liguangpeng (Roc, Network Technology Laboratory)
Re: [Int-area] Using ISO8473 as a network layer t… Carsten Bormann
Re: [Int-area] Using ISO8473 as a network layer t… Alexandre Petrescu
Re: [Int-area] Using ISO8473 as a network layer t… Stewart Bryant
Re: [Int-area] Using ISO8473 as a network layer t… Pascal Thubert (pthubert)
Re: [Int-area] Using ISO8473 as a network layer t… Luigi Iannone
Re: [Int-area] Using ISO8473 as a network layer t… Toerless Eckert
Re: [Int-area] Using ISO8473 as a network layer t… Luigi Iannone
Re: [Int-area] Using ISO8473 as a network layer t… Toerless Eckert
Re: [Int-area] Using ISO8473 as a network layer t… Pascal Thubert (pthubert)
Re: [Int-area] Using ISO8473 as a network layer t… Toerless Eckert