IETF Logo Mail Archive

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

Chris Bowers <cbowers@juniper.net> Tue, 02 September 2014 15:12 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 D5D071A876E; Tue, 2 Sep 2014 08:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 1UcT_DdvdJWp; Tue, 2 Sep 2014 08:12:21 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0242.outbound.protection.outlook.com [207.46.163.242]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9DC41A701F; Tue, 2 Sep 2014 08:12:21 -0700 (PDT)
Received: from DM2PR05MB304.namprd05.prod.outlook.com (10.141.103.24) by DM2PR05MB734.namprd05.prod.outlook.com (10.141.178.22) with Microsoft SMTP Server (TLS) id 15.0.1019.16; Tue, 2 Sep 2014 15:12:20 +0000
Received: from DM2PR05MB303.namprd05.prod.outlook.com (10.141.103.15) by DM2PR05MB304.namprd05.prod.outlook.com (10.141.103.24) with Microsoft SMTP Server (TLS) id 15.0.1019.16; Tue, 2 Sep 2014 15:12:19 +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 15:12:19 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: carrying IPv6 and IPv4 packets using SPRING/SR with MPLS dataplane
Thread-Index: Ac/Gv/F9w1x680bbTQ+xOgAabVdPGQ==
Date: Tue, 02 Sep 2014 15:12:18 +0000
Message-ID: <13e9516b591b49948e5ec155c4b681b4@DM2PR05MB303.namprd05.prod.outlook.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:;UriScan:;
x-forefront-prvs: 0322B4EDE1
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(189002)(199003)(164054003)(31966008)(74662001)(74502001)(15202345003)(108616004)(4396001)(85306004)(19580395003)(33646002)(50986999)(54356999)(99396002)(83322001)(46102001)(110136001)(21056001)(64706001)(85852003)(101416001)(83072002)(90102001)(79102001)(80022001)(15975445006)(2501002)(66066001)(2656002)(86362001)(81542001)(105586002)(81342001)(87936001)(76576001)(20776003)(2351001)(77982001)(229853001)(107046002)(74316001)(95666004)(99286002)(76482001)(92566001)(106356001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB304; H:DM2PR05MB303.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_13e9516b591b49948e5ec155c4b681b4DM2PR05MB303namprd05pro_"
MIME-Version: 1.0
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/nvGgBRpoovf7mfFzY7Q3d_OFSQQ
Cc: "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: [Isis-wg] 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 15:12:26 -0000

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.

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

v2.23.0 | Report a Bug | By Email