IETF Logo Mail Archive

Re: [Isis-wg] [spring] carrying IPv6 and IPv4 packets using SPRING/SR with MPLS dataplane

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Tue, 02 September 2014 16:39 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD4B41A0235; Tue, 2 Sep 2014 09:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.169
X-Spam-Level:
X-Spam-Status: No, score=-15.169 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Eo_JKDhRmJYu; Tue, 2 Sep 2014 09:39:27 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FBF11A011D; Tue, 2 Sep 2014 09:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2546; q=dns/txt; s=iport; t=1409675967; x=1410885567; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BRytTP+uwRhbn2bztwyPgS+3/e+YRrC4/py/cBwKSvI=; b=B4uzar6YUFBsjPEFVomVMvQo5Z1uc8AHbG4vwTv81UFkP2QbFsQW3tK2 hbiNAVYkfw1YWbzUiFjSxlUs4wVizZqfWcIfWCNwpNxP1DYtQ6hhGjG4L IuZdRnHsq6XlBPuDzOGImVrixhm7uNY6rFKLRj69hRWZCGPKMpmJFJbjH g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYFAPjxBVStJA2N/2dsb2JhbABagw1TVwTIGAqGeVMBgRMWd4QDAQEBAwEBAQE3NAsFBwQCAQgOAwQBAQEeCQcnCxQJCAEBBA4FiDoIDbtsARMEjxozBwaDKYEdBZExiyuVHoNhbIFIgQcBAQE
X-IronPort-AV: E=Sophos;i="5.04,450,1406592000"; d="scan'208";a="74280167"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-2.cisco.com with ESMTP; 02 Sep 2014 16:39:26 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s82GdQgX010296 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Sep 2014 16:39:26 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.236]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Tue, 2 Sep 2014 11:39:26 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Chris Bowers <cbowers@juniper.net>
Thread-Topic: [spring] carrying IPv6 and IPv4 packets using SPRING/SR with MPLS dataplane
Thread-Index: Ac/Gv/F9w1x680bbTQ+xOgAabVdPGQAK3cGAAAH0+oAAAMf5gA==
Date: Tue, 02 Sep 2014 16:39:26 +0000
Message-ID: <4A4E21C4-B261-4327-B3C5-AD74D7843B23@cisco.com>
References: <13e9516b591b49948e5ec155c4b681b4@DM2PR05MB303.namprd05.prod.outlook.com> <5FF3A838-09FF-47DA-B516-21F7E3733E22@cisco.com> <153cb0838cff4c8b95afb611689f8e06@DM2PR05MB303.namprd05.prod.outlook.com>
In-Reply-To: <153cb0838cff4c8b95afb611689f8e06@DM2PR05MB303.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.173.109]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3B83152AFF0B9C4BA026F3BDF1373913@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/6jYqIpOqpG_g-nahSqr6e2BVtlE
Cc: "spring@ietf.org" <spring@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] [spring] carrying IPv6 and IPv4 packets using SPRING/SR with MPLS dataplane
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2014 16:39:29 -0000

On Sep 2, 2014, at 6:17 PM, Chris Bowers wrote:
> Stefano,
> 
> Thanks.  Is there a mechanism to advertise different label blocks for v4 and v6 and have a single unique index value associated with the node?


there's a mechanism that allows you to advertise multiple label blocks and the index is used across all of them (see isis/ospf sr extensions drafts). Not sure if you need to explicitly advertise the af of the label block knowing that a sid corresponds to a prefix which implies its af.

s.



>  This would still result in different label values being used for v4 and v6 packets destined for the same node, but the network operator only has to assign a single unique index value to each node.
> 
> Chris
> 
> -----Original Message-----
> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com] 
> Sent: Tuesday, September 02, 2014 10:21 AM
> To: Chris Bowers
> Cc: spring@ietf.org; isis-wg@ietf.org
> Subject: Re: [spring] carrying IPv6 and IPv4 packets using SPRING/SR with MPLS dataplane
> 
> Hi Chris,
> 
> On Sep 2, 2014, at 5:12 PM, Chris Bowers wrote:
>> Has there been any discussion about how to carry both IPv6 and IPv4 packets with SPRING/SR MPLS labels?  From what I can tell, neither draft-filsfils-spring-segment-routing-04 nor draft-filsfils-spring-segment-routing-mpls-03 addresses this scenario.
> 
> 
> sid's are assigned to ip addresses (e.g. intf addresses). A node having two loopbacks (v4/v6) will have a sid for the ipv4 address and another one for the ipv6.
> 
> Then you compute your spt's or explicit paths based on your af-topology and you pick the right sid's stack.
> 
> 
>> In the context of shortest-path forwarding using Node-SID labels, there would seem to be two main approaches to consider.  One could distinguish between IPv6 and IPv4 packets by using two different Node-SID labels for the same node.
> 
> 
> correct. this is same as above: one sid per address (one for v4 and one for v6).
> 
> s.
> 
> 
>> Or one could use IPv6 and/or IPv4 Explicit Null labels pushed on the bottom of the label stack by the SR ingress router.
>> 
>> Do the authors of these drafts or other working group participants have an opinion on the best way to address this scenario?
>> 
>> Thanks,
>> Chris
>> 
>> 
>> 
>> _______________________________________________
>> spring mailing list
>> spring@ietf.org
>> https://www.ietf.org/mailman/listinfo/spring
>

v2.23.0 | Report a Bug | By Email