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

Peter Psenak <ppsenak@cisco.com> Fri, 26 January 2018 15:08 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 5549812D952 for <ospf@ietfa.amsl.com>; Fri, 26 Jan 2018 07:08:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.49
X-Spam-Level:
X-Spam-Status: No, score=-13.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 xtOmI6uHQeTP for <ospf@ietfa.amsl.com>; Fri, 26 Jan 2018 07:08:00 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E223A12D87D for <ospf@ietf.org>; Fri, 26 Jan 2018 07:07:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3547; q=dns/txt; s=iport; t=1516979280; x=1518188880; h=message-id:date:from:mime-version:cc:subject:references: in-reply-to:content-transfer-encoding; bh=Zed6YpAvbTg7WTq9CT9SFRuI2PTZQxMgkvuTA/bGPB0=; b=HFXnJcE5SuCWifdCtnE57Kn+ciUFeBNeTF0mkUp6zHFZhyFPA88vJecA wDqSLmyxv3hUQ0PMY2QedroSUZsByLitMlKO1tT8Cqe8yoUww+QywRdwh vfND+310eqT25mnHe67lZkL4bEQv5qT2ttmg2mhH5T49K/dnffymJm1rI s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOAgAYQ2ta/xbLJq1cGQEBAQEBAQEBAQEBAQcBAQEBAYQodBgPjnWPeZdEFYICChgNhRYCJoJNFwEBAQEBAQEBAmsohRsJAQEEAQE2NgoBEAsYCRYPCQMCAQIBFTATAQUCAQGFb4RCELJHEopYAQEBAQEBAQEBAQEBAQEBASKEUoNsgWcBgy6DLwEBAgEBF4E+g0OCUQWkE4gXjU+CG2eFOYNxJodWjWCJf4E8IQE2JYErMxoIGxUZJIEECIEeCYJMHIFoQDeOLAEBBQ
X-IronPort-AV: E=Sophos;i="5.46,416,1511827200"; d="scan'208";a="1668366"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jan 2018 15:07:58 +0000
Received: from [10.147.24.38] ([10.147.24.38]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w0QF7vIF026778 for <ospf@ietf.org>; Fri, 26 Jan 2018 15:07:57 GMT
Message-ID: <5A6B4455.1060204@cisco.com>
Date: Fri, 26 Jan 2018 16:08:05 +0100
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
CC: ospf@ietf.org
References: <151697898410.24453.1410973838402579492@ietfa.amsl.com>
In-Reply-To: <151697898410.24453.1410973838402579492@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/PPYghlZMM99L9MIjEmwMTtfGYXs>
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-ospfv3-segment-routing-extensions-11.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: Fri, 26 Jan 2018 15:08:02 -0000

Hi,

an updated OSPFv3 SR draft has been posted.

This is a significant rewrite, please read and provide comments.

Summary of the changes:

1. clarified that this draft only specifies the SR extension for MPLS 
data plane. SRv6 extension will be specified in a different document. As 
a result section 3.5 (SR-Forwarding Capabilities) has been removed.

2. SID/Label Sub-TLV code point changed fro 3 to 7, because 3 has been 
defined in draft-ietf-ospf-ospfv3-lsa-extend-23 for Route Tag sub-TLV.

3. SR Local Block Sub-TLV code point changed from 12 to 14 and SRMS 
Preference Sub-TLV code point changed from 13 to 15. These values are 
sharing the same registry with OSPF2 and original values has been taken 
for other extensions.

4. Address Family in OSPFv3 Extended Prefix Range TLV has been defined 
for both IPv4 and IPv6 unicast, IPv4 taking the value 0 and IPv6 taking 
the value 1 (changed from 0). IPv4 AF was added to support the IPv4 
multi-instance case. Value 0 is now consistently used in both OSPFv2 and 
OSPFv3 SR drafts for IPv4 AF.

5 section 6 (SID/Label Binding Sub-TLV) has been removed, similar to 
what has been done for OSPFv2 SR draft.

6 Security Consideration section has been added.

7. References have been updated

8. lots of comments that were addressed in OSPFv2 SR draft during the 
RTGDIR, OPSDIR, GENART, etc., reviews have been incorporated. OSPFv2 and 
OSPFv3 drafts are now back in sync.

thanks,
Peter


On 26/01/18 16:03 , internet-drafts@ietf.org wrote:
>
> 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 WG of the IETF.
>
>          Title           : OSPFv3 Extensions for Segment Routing
>          Authors         : Peter Psenak
>                            Clarence Filsfils
>                            Stefano Previdi
>                            Hannes Gredler
>                            Rob Shakir
>                            Wim Henderickx
>                            Jeff Tantsura
> 	Filename        : draft-ietf-ospf-ospfv3-segment-routing-extensions-11.txt
> 	Pages           : 28
> 	Date            : 2018-01-26
>
> 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 OSPFv3 extensions required for Segment
>     Routing.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-segment-routing-extensions/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-routing-extensions-11
> https://datatracker.ietf.org/doc/html/draft-ietf-ospf-ospfv3-segment-routing-extensions-11
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ospf-ospfv3-segment-routing-extensions-11
>
>
> 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
> .
>