[spring] Flat vs non-flat SIDs
Robert Raszuk <robert@raszuk.net> Sat, 25 September 2021 15:11 UTC
Return-Path: <robert@raszuk.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB923A16AA for <spring@ietfa.amsl.com>; Sat, 25 Sep 2021 08:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=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=raszuk.net
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 YkNfYGiXpuU0 for <spring@ietfa.amsl.com>; Sat, 25 Sep 2021 08:10:57 -0700 (PDT)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B16EF3A16A5 for <spring@ietf.org>; Sat, 25 Sep 2021 08:10:57 -0700 (PDT)
Received: by mail-vs1-xe2b.google.com with SMTP id q66so13245709vsa.4 for <spring@ietf.org>; Sat, 25 Sep 2021 08:10:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:from:date:message-id:subject:to; bh=wWHGHF9aJjAiP8h8F55SWkj4Fp/2yf9K904ZZe59hbU=; b=EHFhbAUZjTySe0i17kjZzF++2J6F+gbHz//b6FNl8vjaIfnw2J81mAPZPijCGFh7ku JIAW/X8djb2u/jZmrBAHQfBqCAlVhhUz5U89sezDsQ53ZMiMmMoa2ytoydeo9ptO4sIu /GLpmqmr+8fgagZfBq2pcxRgjVY0SU441l62pAwMN3Fx3voManBuRCQXxj1QH3t5PqM4 4C6mYykyFJuuiA/AViWZdQBoQDFTC/64JjtJ72HHoN/JwuQKjHC96J+YoGB2otwPKkFx 1o3DHag9Hgr6i5KmA1wS/5iUX2jZPaQC1AdXkGPYqh565266aSExL9KBa2S2XOskKKx7 VD2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wWHGHF9aJjAiP8h8F55SWkj4Fp/2yf9K904ZZe59hbU=; b=Q5C//9D8ezOiKp/BBNSWU5c2umR25AxSHc5HiAAjWnUgtD/K6+6lLw6TpPDIAoTA92 q/xT9XMnMvvmqjdumANspie+a5tGcXP104Y5nRv0trc6Mgjbmi7N+cbV1N76C6SdvJV5 8D1T3jCOXwOz84OUYcT/rDs1vyvMd0fFweV8dxMJfyEpFnkI4foIcsvKZL4VdMFbQeKM xM1iMU5fV5akUQE/HbGaaKmAofLqSPxuunzvUTYNaNBloFYWioflI7O4Ri9IHusoIq99 5nnVcHDPHkh7ZlP2WAnXHNMSSyElhzBsp70YrrgoxHjgks0ooi9AmufYBnEqzgoRzla8 mS6Q==
X-Gm-Message-State: AOAM532b6leLDP3iyQwzTO8v7qMCpMzoBU/7SpCChs8wtf1w9rQUBj+3 nzV2WZkXtgxIQ0UUv5KwpB+FwVYw/Xbr/VhxxZcYklkb/w0XkA==
X-Google-Smtp-Source: ABdhPJyEmpRetvkwQC/Hb7J5swHVoF5ZNKMmz74EdH571BUr/gG93qcasAlwva92gNUTbVrwyU+UiUA/gATCoSs5YUg=
X-Received: by 2002:a05:6102:21b9:: with SMTP id i25mr13917389vsb.1.1632582655968; Sat, 25 Sep 2021 08:10:55 -0700 (PDT)
MIME-Version: 1.0
From: Robert Raszuk <robert@raszuk.net>
Date: Sat, 25 Sep 2021 17:11:35 +0200
Message-ID: <CAOj+MME+YJ9hNgbn6oiTmsoYTdcGjCWQo2qdNd_REybBVpfFqw@mail.gmail.com>
To: SPRING WG <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000469af105ccd345d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ecskHwqk3fowLtag2bD2XjGy8bE>
Subject: [spring] Flat vs non-flat SIDs
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Sep 2021 15:11:03 -0000
All, Watching this discussion on how to compress SIDs (modulo what is the best choice of compressed SID length) a question popped up which perhaps would be very helpful to clarify. SR architecture RFC defines notion of global and local SIDs. Compression analysis discusses state analysis in section 2.3 in respect to global SIDs by listing few parameters N, I, A, D & V which are essentially defining SID applications or types. In all cases the SID or cSID list remains globally flat across all services. Well yes SIDs have some structure via appended function and arguments needed in network programming but the question I am struggling with is not about those. It seems to me that for data plane scaling instead of always constructing huge flat lookup trie it may be quite beneficial to have in the front of each SID a few bits fixed pointer actually directing the real lookup to a proper service or application table. Yes, originally where SR started there was comparison with flat MPLS label space (except that space was always locally significant). Now we are talking globally (within a domain) significant space which does multiply this N times. With that I just want to post this question or really a doubt if no matter what compression is chosen should we not consider to define a fixed demux space which can help to divide and conquer data plane with no worries that if I add few more letters to "N, I, A, D & V chain ... (say S- for slice, G- for 5G, G'-for 6G etc..." my routers are not going to collapse ? Again just to restate I am not talking here to come back to locally significant SIDs. Not at all. Domain wide significant SIDs are cool. I am talking about making the globally significant compressed SIDs to be prepended with notion of service(s) they are constructing in a given network. - - - As we have been via MPLS deployments in the past one of the often requested features was application/services prioritization. If we have one flat SID space this may not be easy. Thx, Robert
- [spring] Flat vs non-flat SIDs Robert Raszuk
- Re: [spring] Flat vs non-flat SIDs Gyan Mishra
- Re: [spring] Flat vs non-flat SIDs Robert Raszuk
- Re: [spring] Flat vs non-flat SIDs Gyan Mishra