Re: [spring] I-D Action: draft-previdi-spring-problem-statement-02.txt

Yakov Rekhter <yakov@juniper.net> Fri, 04 April 2014 20:53 UTC

Return-Path: <yakov@juniper.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927A11A00EF for <spring@ietfa.amsl.com>; Fri, 4 Apr 2014 13:53:38 -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, RCVD_IN_DNSWL_LOW=-0.7, 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 MR0vE4qw-sTK for <spring@ietfa.amsl.com>; Fri, 4 Apr 2014 13:53:33 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id 748331A002F for <spring@ietf.org>; Fri, 4 Apr 2014 13:53:33 -0700 (PDT)
Received: from mail132-ch1-R.bigfish.com (10.43.68.232) by CH1EHSOBE002.bigfish.com (10.43.70.52) with Microsoft SMTP Server id 14.1.225.22; Fri, 4 Apr 2014 20:53:23 +0000
Received: from mail132-ch1 (localhost [127.0.0.1]) by mail132-ch1-R.bigfish.com (Postfix) with ESMTP id 7898C1E0318; Fri, 4 Apr 2014 20:53:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.239.11; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF02-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -1
X-BigFish: VPS-1(zz1432Izz1f42h2148h1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6h208chzzz31h2a8h839h944hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh224fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch25f6h2605h262fh268bh26d3h1155h)
Received-SPF: softfail (mail132-ch1: transitioning domain of juniper.net does not designate 66.129.239.11 as permitted sender) client-ip=66.129.239.11; envelope-from=yakov@juniper.net; helo=P-EMF02-SAC.jnpr.net ; SAC.jnpr.net ;
Received: from mail132-ch1 (localhost.localdomain [127.0.0.1]) by mail132-ch1 (MessageSwitch) id 139664480126009_28313; Fri, 4 Apr 2014 20:53:21 +0000 (UTC)
Received: from CH1EHSMHS012.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.235]) by mail132-ch1.bigfish.com (Postfix) with ESMTP id EC7833202C2; Fri, 4 Apr 2014 20:53:20 +0000 (UTC)
Received: from P-EMF02-SAC.jnpr.net (66.129.239.11) by CH1EHSMHS012.bigfish.com (10.43.70.12) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 4 Apr 2014 20:53:17 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF02-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 4 Apr 2014 13:53:21 -0700
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id s34KrKV56940; Fri, 4 Apr 2014 13:53:20 -0700 (PDT) (envelope-from yakov@juniper.net)
Message-ID: <201404042053.s34KrKV56940@magenta.juniper.net>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
In-Reply-To: <99C71C5C-C367-467D-89DA-D20EA2B92A5E@cisco.com>
References: <20140404193739.20345.19365.idtracker@ietfa.amsl.com> <99C71C5C-C367-467D-89DA-D20EA2B92A5E@cisco.com>
X-MH-In-Reply-To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com> message dated "Fri, 04 Apr 2014 19:39:35 -0000."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <66049.1396644800.1@juniper.net>
Date: Fri, 04 Apr 2014 13:53:20 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/spring/p1bQdoqQC7-gLmbg68FOuFxndmE
Cc: "<spring@ietf.org> ietf.org" <spring@ietf.org>
Subject: Re: [spring] I-D Action: draft-previdi-spring-problem-statement-02.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Apr 2014 20:53:38 -0000

Stefano,


> All,
> 
> this is the new version of the problem-statement draft incorporating 
> the latest comments.

Section 5.1.1.2 is clearly an improvement over what was in the
previous version, although some text is still problematic.
Specifically, "C only installs the path via AS2 in its RIB." If it
is the Adj-RIB-Out, then C wouldn't be able to advertise the path
via AS3 inside AS1 (as this path is not in the Adj-RIB-Out).  And
if it is the Loc-RIB, then the Adj-RIB-Out would have only the path
via AS2 (as the Adj-RIB-Out is populated from the Loc-RIB), and C
would not be able to advertise the path via AS3 inside AS1. Either
way, this would contradict the assumption that "C propagates all
the paths to Z within AS1 (add-path)."

You addressed one part of my comments on section 3. However,
the other part of my comments on section 3 is still not addressed.
Specifically, section 3 of draft-previdi-spring-problem-statement-02 
still contains the following:

   The source-based routing model, applied to the MPLS dataplane, offers
   the ability to tunnel services (VPN, VPLS, VPWS) from an ingress PE
   to an egress PE, with or without the expression of an explicit path
   and without requiring forwarding plane or control plane state in
   intermediate nodes.

The above claim about the ability to tunnel services is misleading,
as VPN and VPLS services may use p2mp or (in the case of VPN) mp2mp
LSPs, and providing any capability for setting up such LSPs is not
in the SPRING charter.

With this in mind I propose to replace the above with the following:

   The source-based routing model, applied to the MPLS dataplane, offers
   the ability to tunnel services (VPN, VPLS, VPWS) from an ingress PE
   to an egress PE, with or without the expression of an explicit path
   and without requiring forwarding plane or control plane state in
   intermediate nodes, but only if such tunnels are neither p2mp
   nor mp2mp tunnels.

Yakov.