Re: [mpls] [spring] [SPRING] Query related to SR Architecture

Robert Raszuk <robert@raszuk.net> Thu, 10 September 2015 15:46 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91ECC1B53D8; Thu, 10 Sep 2015 08:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 gg9ifAFZeFdS; Thu, 10 Sep 2015 08:46:28 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (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 627F01B428E; Thu, 10 Sep 2015 08:46:28 -0700 (PDT)
Received: by wicfx3 with SMTP id fx3so33336629wic.1; Thu, 10 Sep 2015 08:46:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Bgbs2MI+WW9uFgKelkrrm5ht2CjDQMsO+f2a9Wf1wWE=; b=Ud6hQYxlCp6/BS1yyhUSA6F9Tkv2J/zN5OdbwJbiSSUZMD/mfu1JVX+0f/Fu3/vMOM YyFvObenVll7jLZ+B8Q8R49QjT3iBZFKpNrwPxZqTX1givN3ZuksyxkREgHt99k/7MOj KdImTrMv3qehJ4A6s6Ak5ZRnQygiRWcdqwkUg9VXcJj0j5fSnBb+TYouZtUixWS6uOgf BJiksciiMDC04DyYoGXnVO0dFHKA+Mb7ljIkpx5uNYUs/rKF4LbmaS/4iGUojM+aCSdb n9pk1xINaP8SeT5f1GSG1KytVHreYsUl9miL+KFdozmpJSlMm+NEN8ng6H/iTiZlPahL +35g==
MIME-Version: 1.0
X-Received: by 10.194.122.97 with SMTP id lr1mr71287470wjb.26.1441899986165; Thu, 10 Sep 2015 08:46:26 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.194.37.5 with HTTP; Thu, 10 Sep 2015 08:46:26 -0700 (PDT)
In-Reply-To: <327562D94EA7BF428CD805F338C31EF06C04975F@nkgeml512-mbx.china.huawei.com>
References: <544F5E3F-82AD-49BA-A83B-201DE49A08A6@juniper.net> <327562D94EA7BF428CD805F338C31EF06C0496F5@nkgeml512-mbx.china.huawei.com> <99EAE216-DB6C-4AFD-8E5C-E834D68CBF52@juniper.net> <327562D94EA7BF428CD805F338C31EF06C04975F@nkgeml512-mbx.china.huawei.com>
Date: Thu, 10 Sep 2015 17:46:26 +0200
X-Google-Sender-Auth: IiEVSLk0gJuVZqZG3stcGk4is5s
Message-ID: <CA+b+ER=Si4E8xQKkXs_u7M2s1Au_qeM_kk3YCtS0AfvN0xjViQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
Content-Type: multipart/alternative; boundary="089e01228c707a283f051f6680dd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/2MMdF9lPqRKMkdfycll6r4fy4hQ>
Cc: "mpls@ietf.org" <mpls@ietf.org>, Gaurav agrawal <gaurav.agrawal@huawei.com>, "spring@ietf.org" <spring@ietf.org>, Vinod Kumar S 70786 <v70786@notesmail.huawei.com.cn>, Pushpasis Sarkar <psarkar@juniper.net>
Subject: Re: [mpls] [spring] [SPRING] Query related to SR Architecture
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 15:46:29 -0000

Hi Anil,

Another possibility here would be to allocate not 1 but 10 SR labels for a
given segment and embed the service notion in it. For 10 services I think
the scale is ok. Perhaps for 1000 services this could bring label space
scaling concerns, but this is very specific to particular deployment.

That way on the packet you will have label stack of 1 label (not two) and
have at the imposition point 10 labels getting the packets to particular SR
node/link while also transporting the information about service selection
to be performed at each service aware transit or SR node.

Best,
R.