IETF Logo Mail Archive

Re: [OSPF] WG Adoption Poll for "Using Operator-defined TLVs for Agile Service Deployment"

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Thu, 17 March 2016 04:40 UTC

Return-Path: <ginsberg@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 4A57B12DAEF for <ospf@ietfa.amsl.com>; Wed, 16 Mar 2016 21:40:35 -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_PASS=-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 SMSMXygkGtMi for <ospf@ietfa.amsl.com>; Wed, 16 Mar 2016 21:40:32 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 388A112DB2F for <ospf@ietf.org>; Wed, 16 Mar 2016 21:40:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2866; q=dns/txt; s=iport; t=1458189632; x=1459399232; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=C3V83Y5ivAXoedu4RWnDuRSjRj98klZf9V7BOKE3CNs=; b=MQ430fAATYCXVJhCM1duXd36UfRHqPGpswslXY1/ilXsC8eXiJVKkEfH F+fQjjIe6dj9m+uC5puIU6ICpaHMFwHeSABQf6cv/6IT5sgemJ9bs7JAi 30zBp1GQADD3ACSVPIv5ij+MD000HfucG2vgU8mOQBqulm7Nmt/TVm+pr k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ABAgA4NOpW/5BdJa1eg0ZTbga6CwENgW8XCoVsAhyBHjgUAQEBAQEBAWQnhEEBAQEEAQEBIBE6FwQCAQgRBAEBAwIjAwICAiULFAEICAIEARIIiB8OsQOPQwEBAQEBAQEBAQEBAQEBAQEBAQEBAREEfIUihESHPIE6BZdSAY15gWyESYhXjwEBHgEBQoIwgTVqiWV+AQEB
X-IronPort-AV: E=Sophos;i="5.24,348,1454976000"; d="scan'208";a="83653292"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Mar 2016 04:40:31 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u2H4eVMl026810 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ospf@ietf.org>; Thu, 17 Mar 2016 04:40:31 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 16 Mar 2016 23:40:30 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1104.009; Wed, 16 Mar 2016 23:40:30 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, OSPF WG List <ospf@ietf.org>
Thread-Topic: WG Adoption Poll for "Using Operator-defined TLVs for Agile Service Deployment"
Thread-Index: AQHRf/Ho6WRxQA5zQE2bUJRokiTbP59dC0kg
Date: Thu, 17 Mar 2016 04:40:30 +0000
Message-ID: <e1c1685f2856424c939bfbea4a5d90a3@XCH-ALN-001.cisco.com>
References: <D30F89DE.51A65%acee@cisco.com>
In-Reply-To: <D30F89DE.51A65%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.92.7]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/AyZ8bmBikLOccWTjY4gpOxJIKCE>
Subject: Re: [OSPF] WG Adoption Poll for "Using Operator-defined TLVs for Agile Service Deployment"
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 17 Mar 2016 04:40:35 -0000

My opinion of the draft has not changed.

It is defining a way to utilize OSPF to send application information - which is not something the protocol should be used to do.
Further, it leaves definition of the new codepoints and formats of the information advertised completely unspecified - the latest draft revision states:

" The meaning of the operator-defined sub-TLV is totally opaque to OSPF
   and is defined by the network local policy and is controlled via
   configuration.  "

How interoperability is achieved is not addressed at all.

IS-IS has taken a much more stringent approach to a similar request. 	
RFC 6823 (GENAPP) requires that information sent in the generic container TLV MUST be based on a public specification - and that an application specific ID for the application using this mechanism be assigned by IANA. This addresses the interoperability issue.
GENAPP further specifies that such information SHOULD be advertised by a separate instance of the routing protocol (as specified in RFC 6822(MI)) so as to minimize the impact of the application information flooding on the performance of the routing protocol.

Without addressing both of these issues I cannot support the draft.

   Les


> -----Original Message-----
> From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem
> (acee)
> Sent: Wednesday, March 16, 2016 7:09 PM
> To: OSPF WG List
> Subject: [OSPF] WG Adoption Poll for "Using Operator-defined TLVs for Agile
> Service Deployment"
> 
> We’ve discussed this draft a number of times. In my opinion, it seems like a
> useful mechanism if one envisions a generalized API between OSPF and user
> and third-party applications to convey application-specific information
> learned from other OSPF routers. In many respects, this has already been
> envisioned for OSPF Node Tags. Please indicate your opinion on this draft
> before March 31st, 2016.
> 
> Thanks,
> Acee
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf

v2.23.0 | Report a Bug | By Email