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

Chris Bowers <cbowers@juniper.net> Tue, 02 September 2014 16:17 UTC

Return-Path: <cbowers@juniper.net>
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 184F21A0700; Tue, 2 Sep 2014 09:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 I5nnSwbZd3wy; Tue, 2 Sep 2014 09:17:05 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0141.outbound.protection.outlook.com [207.46.163.141]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A33CA1A06EE; Tue, 2 Sep 2014 09:17:04 -0700 (PDT)
Received: from DM2PR05MB303.namprd05.prod.outlook.com (10.141.103.15) by DM2PR05MB302.namprd05.prod.outlook.com (10.141.103.12) with Microsoft SMTP Server (TLS) id 15.0.1015.19; Tue, 2 Sep 2014 16:17:02 +0000
Received: from DM2PR05MB303.namprd05.prod.outlook.com ([10.141.103.15]) by DM2PR05MB303.namprd05.prod.outlook.com ([10.141.103.15]) with mapi id 15.00.1019.015; Tue, 2 Sep 2014 16:17:02 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Thread-Topic: [spring] carrying IPv6 and IPv4 packets using SPRING/SR with MPLS dataplane
Thread-Index: AQHPxsGIbHxG5LVgDE+GjGvmzRmylpvt/13w
Date: Tue, 02 Sep 2014 16:17:01 +0000
Message-ID: <153cb0838cff4c8b95afb611689f8e06@DM2PR05MB303.namprd05.prod.outlook.com>
References: <13e9516b591b49948e5ec155c4b681b4@DM2PR05MB303.namprd05.prod.outlook.com> <5FF3A838-09FF-47DA-B516-21F7E3733E22@cisco.com>
In-Reply-To: <5FF3A838-09FF-47DA-B516-21F7E3733E22@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [66.129.239.10]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;
x-forefront-prvs: 0322B4EDE1
x-forefront-antispam-report: SFV:NSPM; SFS:(979002)(6009001)(24454002)(377454003)(199003)(51704005)(164054003)(189002)(13464003)(4396001)(74662001)(83072002)(101416001)(90102001)(64706001)(83322001)(80022001)(79102001)(87936001)(74502001)(77982001)(81542001)(85306004)(85852003)(19580405001)(81342001)(20776003)(46102001)(15975445006)(76482001)(2656002)(21056001)(86362001)(33646002)(99396002)(50986999)(95666004)(54356999)(76176999)(92566001)(110136001)(19580395003)(99286002)(106116001)(31966008)(108616004)(66066001)(76576001)(105586002)(106356001)(74316001)(107046002)(24736002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB302; H:DM2PR05MB303.namprd05.prod.outlook.com; FPR:; MLV:ovrnspm; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/JdpB3P40K8keKAFiRlIFsOX4p2E
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:17:07 -0000

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?  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