Re: [OSPF] AD review of draft-ietf-ospf-encapsulation-cap-03

"Acee Lindem (acee)" <> Tue, 20 June 2017 02:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 58290131900; Mon, 19 Jun 2017 19:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.522
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, HTML_MESSAGE=0.001, 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, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gGTSl2fLAN6n; Mon, 19 Jun 2017 19:44:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 395A4131902; Mon, 19 Jun 2017 19:44:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=44829; q=dns/txt; s=iport; t=1497926690; x=1499136290; h=from:to:subject:date:message-id:mime-version; bh=Ss2ORz6mn+0PHNoEi526mZ21ffazdHS5tyAcMGloFXQ=; b=b51SjF9F9SL8fA6WHNs27D1Bjp2QGUau3YzIkPw8gxSzGu5iFiuTIMLY 9m/NZqPLNuZprKJMX6zLty3V98Z5jx2wIo84RCq/LE73hmYDxmsd7dEQ/ zKAPKCfeTh5YOMZSLl6WfMcW6d4M4ADqm8O2KLGZQ3e4MP4SUuAm8oc/Q I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.39,363,1493683200"; d="scan'208,217";a="249564844"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jun 2017 02:44:48 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v5K2imMT014200 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 20 Jun 2017 02:44:48 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 19 Jun 2017 22:44:47 -0400
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Mon, 19 Jun 2017 22:44:47 -0400
From: "Acee Lindem (acee)" <>
To: Xuxiaohu <>, Alia Atlas <>, OSPF List <>, "" <>
Thread-Topic: [OSPF] AD review of draft-ietf-ospf-encapsulation-cap-03
Thread-Index: AQHS6W8uwTdS+O6UOkGzV2DRDznJvQ==
Date: Tue, 20 Jun 2017 02:44:47 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D56E03BFB5CD5aceeciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [OSPF] AD review of draft-ietf-ospf-encapsulation-cap-03
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Jun 2017 02:44:54 -0000

Hi Tiger/Bruno,

See one inline.

From: OSPF <<>> on behalf of Xiaohu Xu <<>>
Date: Monday, June 19, 2017 at 9:19 PM
To: Alia Atlas <<>>, OSPF WG List <<>>, "<>" <<>>
Subject: Re: [OSPF] AD review of draft-ietf-ospf-encapsulation-cap-03

Hi Alia,

Thanks a lot for your AD review. Please see our response inline.

发件人: Alia Atlas []
发送时间: 2017年6月15日 6:56
收件人: OSPF List;<>
主题: AD review of draft-ietf-ospf-encapsulation-cap-03

As is customary, I have done my AD review of draft-ietf-ospf-encapsulation-cap-03.
First, I would like to thank the authors - Xiaohu, Bruno, Robert, Luis, and Luay - for their work on this useful document.

I do have a few concerns that need addressing before the draft can progress.

[Bruno/Xiaohu] Many thanks for your useful comments.
Following your comments, we believe it would be simpler and better to not create a new IANA registry for ”IGP  Tunnel Encapsulation Attribute Types” but rather reuse the existing BGP one:

[Bruno/Xiaohu] BTW when this OSPF extension has been defined, it has been modeled based on RFC 5512. However, as of today, the BGP extension is been redefined in draft-ietf-idr-tunnel-encaps, sometimes. Which normative reference should be use?
- as of today, RFC 5512 is probably the right one as draft-ietf-idr-tunnel-encaps has not passed WG LC and may never be published as RFC (IDR requires 2 implementations. I think RFC 5512 has not been implemented hence we may question whether draft-ietf-idr-tunnel-encaps will be…)
- in some hypothetical future, draft-ietf-idr-tunnel-encaps may obsolete RFC 5512

I agree that you should use RFC 5512 as that is the RFC that created the reference. At this point, the status of draft-ietf-idr-tunnel-encaps is irrelevant.



1)  First, the draft talks about what information is sent - but nothing about how it is to be understood or used.  That'd be ok if there were a clear reference to a document that discussed the related procedures.  A quick scan of draft-ietf-idr-tunnel-encaps-06 seems that it may be the right place to start - but it's procedures are BGP-focused and while there are many similarities, there may be interesting differences as well.

[Bruno/Xiaohu] We’ll clarify that the 3 sub-TLV (§5.1-§5.3) are normatively defined in RFC 5512, from a format, semantic and usage standpoint. And that there code point are allocated in respectively the following IANA registries: BGP Tunnel Encapsulation Attribute Tunnel Types, BGP Tunnel Encapsulation Attribute Sub-TLVs. As per you comment, we need to clarify the 5.4 color Sub-TLV. Proposed text:
The Color Sub-TLV value is a 4-octet unsigned integer. Its semantic and usage are the same as the Color Value, from the Color Sub-TLV defined in RFC 5512 section 4.3 (*)

For instance, for the Color sub-TLV, is the 4 byte color value expected to represent the same meaning in OSPF as in BGP?


  Can a BGP route with a particular color extended community then have the OSPF tunnel to use selected from only those tunnels with the same color?

  What does the Color TLV mean in a purely OSPF context?

[Bruno/Xiaohu] idem as in the IDR context.  It’s a color used to define policy. The application using those tunnels, may use this color as an input for its policy when choosing the tunnel to use (or not use).
We can add this text if needed.

  Sec 7 of draft-ietf-idr-tunnel-encaps-06 ("However, suppose that one of the TLVs in U2's Tunnel Encapsulation attribute contains the Color Sub-TLV.  In that case, packet P SHOULD
   NOT be sent through the tunnel identified in that TLV, unless U1 is
   carrying the Color Extended Community that is identified in U2's
   Color Sub-TLV.") doesn't seem to strictly apply.

[Bruno/Xiaohu] Would new clarification added above (*) be enough? If not, a priori, I’d rather improve the definition of section 5.4 defining this color sub-TLV, in order for it to generally apply to any text. (rather than trying to patch the specific above text from Sec 7)

Semantics and behavior need to be specified - not just the encodings, and that is all this draft currently has.

2)  Sec 5.1 and Sec 5.2 refer to the format of the Encapsulation Sub-TLV and Protocol Sub-TLV coming from draft-ietf-idr-tunnel-encaps-06 - but that draft defines not merely the format, but allocates an IANA registry for additional sub-types that can appear and defines the format and contents of the sub-TLV based upon the tunnel type.   I'm nearly certain that you mean that these sub-tlvs use not merely the same format (does variable length fields based upon the allocated type cause issues for OSPF sub-TLV parsing???) but can contain any values and sub-TLVs defined in the relevant IANA registry. As it is written now, there is no reference to the registry or ability to easily support more tunnel types in the future.

[Bruno/Xiaohu] Good point. Does the previous change address that point?

3) It is unfortunate that Geneve, which is the agreed encapsulation for NVO3, is not included in the set of tunnels but VXLAN-GPE, which is not going to be a standard, is.
I know this is duplicating what is in draft-ietf-idr-tunnel-encaps-06 but it emphasizes the need to assume additional Tunnel Types and related Encapsulation Sub-TLVs will be defined.

[Bruno/Xiaohu] I agree that this is unfortunate.
But as the this new change, this draft will just refer to the existing BGP tunnels types. No duplication, no new tunnel types.
I’d rather define new types in an independent document. Home of this document, and possibly additional WGs to cross-post, would already be a good question ;-) (candidates could be OSPF, IS-IS, IDR, NVO3, RTGWG, softwires, possibly BESS…)

4) Sec 4: Is there a reason to create a new IGP Tunnel Encapsulation Types registry instead of reusing BGP Tunnel Encapsulation Attribute Tunnel Types (  The latter is FCFS and the proposed registry is Standards Action.   There are already differences and collisions between the two (i.e. value 15).
What would happen if an Encapsulation Sub-TLV needed to include a Tunnel Type? Which registry would it pull from? Would the value used depend on the protocol it was signaled in?

[Bruno/Xiaohu] Not anymore. (in early version of the OSPF draft, the code point was 1 octet, while IDR was 2). As indicated above, we’ll change to use the BGP one.

5) I-D.ietf-idr-tunnel-encaps has to be a normative reference.

[Bruno/Xiaohu] see the above.

6) Given that some of the references are to in progress documents for the tunnel types, is it expected that the values will correspond to future versions or are they nailed to this particular version or something else?

[Bruno/Xiaohu] I think the reference to existing “BGP”/IANA registry address this point


a) Sec 1:"Partial deployment of IPv6 in IPv4 networks or IPv6 in IPv4
      networks as described in [RFC5565]"
s/IPv6 in IPv4/IPv4 in IPv6 for one of the two

[Bruno/Xiaohu] will fix it. Thanks again for your detailed AD review of this doc.


Best regards,