Re: [spring] FW: New Version Notification for draft-gulkohegde-routing-planes-using-sr-00.txt

Pushpasis Sarkar <pushpasis.ietf@gmail.com> Tue, 14 March 2017 07:20 UTC

Return-Path: <pushpasis.ietf@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1C81289B0 for <spring@ietfa.amsl.com>; Tue, 14 Mar 2017 00:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jkYnO1oQgwpt for <spring@ietfa.amsl.com>; Tue, 14 Mar 2017 00:20:30 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (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 CE702126CD8 for <spring@ietf.org>; Tue, 14 Mar 2017 00:20:29 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id l37so117810755wrc.1 for <spring@ietf.org>; Tue, 14 Mar 2017 00:20:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MujYTz9hcwyCV/Y96FgZWm3d2LjjwIEt08mMgWJxxYc=; b=CtBRR24JdSKfgOh6ZsqB3ZqQjfyNkXWiueF/+jyG3n2jK3UoDzXgxqiV39ISUD/Ujq q/nfyi2LM8+8gRxmjv4V610QnH/Zjv0RBiRxvYMgMxRT9HuErzPABH5T44vnCXOyCZ/E r8mhdjrcivl7tYZk1a6hBez6I+t3VOBsfgSMTO8wkYfkkFT6F4kqQr09MdmS7kgqJCp9 6ql8XPJyIEolW9L+LWJVte8NVPV3R+SrY7L+gSxINMy16vhCTWNBGRMeJ2pQvasBeaW/ eGzLjV6WZOFi38gkqoNGYcQqBQ6PaRteKZ/FkuJqyOLnAK8+VTjZc6HELuKJjnQY1yuG t9Ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MujYTz9hcwyCV/Y96FgZWm3d2LjjwIEt08mMgWJxxYc=; b=sSsXI3fXyDzXYKibZxo6KuK6bxkTYbHfbuZtmsajKLE5dZDwyeM0wYrdu6ASHcc9Dc nOYT51PT6qsGX7Chx6obfPa5dzGwphQbKpIdbW/0KOS3qn5GiM9JdnGl5WGrNyH9Xyo4 Kw1HASqxTlTDpnOHtUQ3o+YK4NN+cS1eZRwIhrvgZaVUp3xKwB3JI5wc1bS3PcVd3k5m JGmyYY4mH88Eu6300hB+UtSKD2/Z4fKxc+bkKgucnAziQwEC9XtikNgVS8TREg7dfXM7 56bp6WVaCYqFhAmyUmPSy9VRky/LoNr1IShLWocFOnrcKPWG8Yjpb6sM6BvujhPUy9DP 203g==
X-Gm-Message-State: AMke39mh3gqvcdKrXnSWb5HL/WHKwO8ia1TsHxmiGGnepySoDz7UXksBtx0yILLwUnt4AhWyvbbVssxmuAax2w==
X-Received: by 10.223.147.66 with SMTP id 60mr31538909wro.173.1489476028346; Tue, 14 Mar 2017 00:20:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.173.50 with HTTP; Tue, 14 Mar 2017 00:20:27 -0700 (PDT)
In-Reply-To: <BN3PR05MB2706C7B0F310EBA26BA03652D5240@BN3PR05MB2706.namprd05.prod.outlook.com>
References: <148942959391.9235.4676422773984365529.idtracker@ietfa.amsl.com> <BN3PR05MB2706C7B0F310EBA26BA03652D5240@BN3PR05MB2706.namprd05.prod.outlook.com>
From: Pushpasis Sarkar <pushpasis.ietf@gmail.com>
Date: Tue, 14 Mar 2017 00:20:27 -0700
Message-ID: <CAEFuwkgJheR7RLt=DazjAe5n=cSY3Kj=wxaziJYfA=LxZRbVSA@mail.gmail.com>
To: Shraddha Hegde <shraddha@juniper.net>
Content-Type: multipart/alternative; boundary="94eb2c0d9e8a923872054aaba913"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/w7TGNTodQSgEf7PGg4HxHtHa_JU>
Cc: "spring@ietf.org" <spring@ietf.org>, "arkadiy.gulko@thomsonreuters.com" <arkadiy.gulko@thomsonreuters.com>
Subject: Re: [spring] FW: New Version Notification for draft-gulkohegde-routing-planes-using-sr-00.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 14 Mar 2017 07:20:32 -0000

Hi Authors,

First I must admit that I have not read the entire draft in details...

But from the abstract it seems that for the problem that this draft is
trying to address, a similar problem is already addressed in the Segment
Routing Problem Statement and Use-Case document (RFC 7855, section 3.3.1.1.1.
Disjointness in Dual-Plane Networks). And the same has been solved using
any cast segments as specified in draft-ietf-spring-mpls-anycast-segment.

Request you to clarify why we need the solution proposed in this draft over
the one proposed in draft-ietf-mpls-anycast-segments..

Thanks and Best regards,
-Pushpasis


On Mon, Mar 13, 2017 at 8:25 PM, Shraddha Hegde <shraddha@juniper.net>
wrote:

> Hi All,
>
> New draft submitted for "separating routing planes using segment routing".
> Looking for inputs and comments.
>
> PS: The draft erroneously got submitted as individual and not affiliated
> to any WG but the intention was to submit it to SPRING WG.
> We will correct it once the submission window opens. Apologies for the
> inconvenience.
>
> Rgds
> Shraddha
>
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, March 13, 2017 11:57 PM
> To: arkadiy.gulko@thomsonreuters.com <arkadiy.gulko@thomsonreuters.com>;
> Shraddha Hegde <shraddha@juniper.net>; Arkadiy Gulko <
> arkadiy.gulko@thomsonreuters.com>
> Subject: New Version Notification for draft-gulkohegde-routing-
> planes-using-sr-00.txt
>
>
> A new version of I-D, draft-gulkohegde-routing-planes-using-sr-00.txt
> has been successfully submitted by Shraddha Hegde and posted to the IETF
> repository.
>
> Name:           draft-gulkohegde-routing-planes-using-sr
> Revision:       00
> Title:          Separating Routing Planes using Segment Routing
> Document date:  2017-03-13
> Group:          Individual Submission
> Pages:          7
> URL:            https://www.ietf.org/internet-drafts/draft-gulkohegde-
> routing-planes-using-sr-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-gulkohegde-routing-
> planes-using-sr/
> Htmlized:       https://tools.ietf.org/html/draft-gulkohegde-routing-
> planes-using-sr-00
>
>
> Abstract:
>    Many network deployments arrange the network topologies in two or
>    more planes.  The traffic generally uses one of the planes and fails
>    over to the other plane when there are link or node failure.  Certain
>    applications require the traffic to be strictly restricted to a
>    particular plane and should not failover to the other plane.  This
>    document proposes a solution for the strict planar routing using
>    Segment Routing.
>
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>