Subject: Re: [Srcomp] REQ-8-1-INTERWORKING-DOMAINS-00

From: Ron Bonica <[email-masked]>
Date: Mon, 3 Aug 2020 14:26:25 +0000

Hello Peng,

I support this requirement 100%.

At implementation time, it will raise an interesting issue, but that issue is unavoidable. When sending a packet across domain boundaries, how will the SR Path be encoded:

  *   Using the sender's encoding mechanism?
  *   Using the receiver's encoding mechanism?
  *   Using a common encoding mechanism that may be native to neither the sender nor the receiver?

                                                                                           Ron

Juniper Business Use Only
From: Srcomp <[email-masked]> On Behalf Of [email-masked]
Sent: Friday, July 31, 2020 11:09 PM
To: [email-masked]
Subject: [Srcomp] REQ-8-1-INTERWORKING-DOMAINS-00

[External Email. Be cautious of content]

Short Name: Interworking Across SR Domain Boundaries.

Description: An E2E SR path may across multiple domains and each domain has different SID encapsulation style.

Rational: SRv6 is deployed in the network gradually, there maybe already deployed calssical 128-bits based SID SRv6 solution in some domains, and may also deployed SR-MPLS in other domains, thus if an E2E SR path across multiple domains, the new compression-based SID SRv6 solution MUST support interworking with other classical SRv6 and SR-MPLS domains in the network. If the new compression-based SID SRv6 provide multiple compression length, eg, 32, 16, etc, multiple domains each with different compression length MUST also support interworking between them. Note that the classical 128-bits SID based SID SRv6 solution can be considered to have a compression length of 128.

Metric: The solution must provide method to interwork with classical SRv6 or SR-MPLS domains, and interwork between domains with different compression length.

Regards,

PSF