Re: [OSPF] I-D Action: draft-ietf-ospf-segment-routing-extensions-13.txt

Peter Psenak <ppsenak@cisco.com> Wed, 10 May 2017 07:02 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D910129AD2; Wed, 10 May 2017 00:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 22xMrCs5mRky; Wed, 10 May 2017 00:02:43 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 500C9120454; Wed, 10 May 2017 00:02:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4075; q=dns/txt; s=iport; t=1494399762; x=1495609362; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=7nLtHv8To1xpW4Fio0hUdNTQcTJo/dT0nEZVaH9oW2c=; b=STe0wBIiLXjVxZHAJuqmhLpyXzMFMhFv7VNvMT2K+adwCAynw+lB4V9U AeGZp18CsKLnEW+PsoVygHjLsC3HvaRa4dbeCHOW9ABcfWUgXq3Faua+5 sI0yCRn6GlNGDPBxEMOOxdmDUbq2rFqBGwGp+VFixsSGS4gPejakJvo9q Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CMAACxuRJZ/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhDeBDI4Bc5BilXKCDyENhXYChTIYAQIBAQEBAQEBayiFFQEBAQE?= =?us-ascii?q?DAQE2NgoBDAQLEQQBAQEJFggHCQMCAQIBFR8JCAYBDAEFAgEBih0OtFISinQBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEdhl+BXYMcgyGBLDyFSAEEngWHHIt+ggRVhGa?= =?us-ascii?q?DQ4ZplEIfOIEKLyAIGRUcKoR2HIFlPjaJGQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,318,1491264000"; d="scan'208";a="652769455"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2017 07:02:37 +0000
Received: from [10.60.140.57] (ams-ppsenak-nitro8.cisco.com [10.60.140.57]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v4A72b62007447; Wed, 10 May 2017 07:02:37 GMT
Message-ID: <5912BB0E.6070805@cisco.com>
Date: Wed, 10 May 2017 09:02:38 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Shraddha Hegde <shraddha@juniper.net>, "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
CC: "ospf@ietf.org" <ospf@ietf.org>
References: <149389189879.4821.567420168746411343@ietfa.amsl.com> <BN3PR05MB2706DD1C3249BDE683DF62E3D5EC0@BN3PR05MB2706.namprd05.prod.outlook.com>
In-Reply-To: <BN3PR05MB2706DD1C3249BDE683DF62E3D5EC0@BN3PR05MB2706.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/a1Koo_S0xOHoJheGjE_xVJocpP4>
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-segment-routing-extensions-13.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 May 2017 07:02:45 -0000

Hi Shraddha,

please see inline:

On 10/05/17 07:34 , Shraddha Hegde wrote:
> Authors,
>
> Apologies for being late with this comment in the process of standardization.
>
> The below section 5 describes the PHP for mapping server
>
>
> " As the Mapping Server does not specify the originator of a prefix
>     advertisement, it is not possible to determine PHP behavior solely
>     based on the Mapping Server advertisement.  However, PHP behavior
>     SHOULD be done in following cases:
>
>        The Prefix is intra-area type and the downstream neighbor is the
>        originator of the prefix.
>
>        The Prefix is inter-area type and downstream neighbor is an ABR,
>        which is advertising prefix reachability and is also generating
>        the Extended Prefix TLV with the A-flag set for this prefix as
>        described in section 2.1 of [RFC7684]."
>
>
> The text says "PHP behavior" should be done in following cases.
> In the second case here it's an ABR re-advertising a prefix and SID being advertised for this
> Prefix from a mapping server. If we interpret "PHP behavior should be done"
> As the penultimate router removing the label and forwarding the packet to ABR,
> It does not work since the inner labels gets exposed at the ABR.

above texts clearly specifies that PHP is done only for case where ABR 
is originating a prefix, not propagating it from other area. You can 
distinguish between the two based on the A-flag in the Extended Prefix 
TLV as specified in RFC7684, which the above text mentions.

thanks,
Peter
>
> Request authors to add clarification text around "PHP behavior".
>
> Rgds
> Shraddha
>
> -----Original Message-----
> From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Thursday, May 4, 2017 3:28 PM
> To: i-d-announce@ietf.org
> Cc: ospf@ietf.org
> Subject: [OSPF] I-D Action: draft-ietf-ospf-segment-routing-extensions-13.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Open Shortest Path First IGP of the IETF.
>
>          Title           : OSPF Extensions for Segment Routing
>          Authors         : Peter Psenak
>                            Stefano Previdi
>                            Clarence Filsfils
>                            Hannes Gredler
>                            Rob Shakir
>                            Wim Henderickx
>                            Jeff Tantsura
> 	Filename        : draft-ietf-ospf-segment-routing-extensions-13.txt
> 	Pages           : 35
> 	Date            : 2017-05-04
>
> Abstract:
>     Segment Routing (SR) allows a flexible definition of end-to-end paths
>     within IGP topologies by encoding paths as sequences of topological
>     sub-paths, called "segments".  These segments are advertised by the
>     link-state routing protocols (IS-IS and OSPF).
>
>     This draft describes the OSPF extensions required for Segment
>     Routing.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ospf-segment-routing-extensions/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-ospf-segment-routing-extensions-13
> https://datatracker.ietf.org/doc/html/draft-ietf-ospf-segment-routing-extensions-13
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ospf-segment-routing-extensions-13
>
>
> 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.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
> .
>