Subject: Re: [Srcomp] REQ-7-28-FLEX-ADDRESS-PLANNING-00

From: "Chengli (Cheng Li)" <[email-masked]>
Date: Mon, 3 Aug 2020 12:23:42 +0000

Hi Ron，

I think you are correct. When merging two SRv6 networks into one, it will be good to reuse the existing IPv6 addresses instead of renumbering.

Thanks,
Cheng

From: Ron Bonica [mailto:[email-masked]]
Sent: Thursday, July 30, 2020 2:59 AM
To: Chengli (Cheng Li) <[email-masked]>; [email-masked]
Subject: RE: [Srcomp] REQ-7-28-FLEX-ADDRESS-PLANNING-00

Cheng Li,

I strongly support this requirement. In fact, I would like to add two metrics.

Assume that two companies run SRv6 networks. One company draws it locators from the prefix 2001:db8::/48, while the other draws its locators from the prefix 2001:db8:FFFF:FF00::/56. At some point, the companies want to merge their networks into a single SRv6 domain.

Metric 1: The merger must not require renumbering of either network. The compression mechanism must continue to work, even though locators have different lengths.

Metric 2: The merger must not require renumbering of either network. Compression efficiency must not be effected by the merger.

Juniper Business Use Only
From: Srcomp <[email-masked]<mailto:[email-masked]>> On Behalf Of Chengli (Cheng Li)
Sent: Tuesday, July 28, 2020 9:47 AM
To: [email-masked]<mailto:[email-masked]>
Subject: [Srcomp] REQ-7-28-FLEX-ADDRESS-PLANNING-00

[External Email. Be cautious of content]

Short Name: Flexible IPv6 address Planning

Description: The compression mechanism MUST support flexible IPv6 address planning, and MUST NOT require for specific address type and address value. Also, It MUST support to be deployed by using GLA, ULA and other unicast address types.

Rationale: The address planning of the network is vary based on the address schema of the operator, so the solution MUST support flexible address planning. Operators need to deploy the solution based on their own addresses planning.

Metric: if the solution only works when using a specific address type, or some specific address value, that is not compliant. If it require one or some specific prefixes, that is not compliant.

Cheng