Re: [OSPF] OSPF Operator-Defined TLVs (https://www.ietf.org/id/draft-chunduri-ospf-operator-defined-tlvs-01.txt)
"Acee Lindem (acee)" <acee@cisco.com> Mon, 19 October 2015 21:29 UTC
Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5E91B2CC6 for <ospf@ietfa.amsl.com>; Mon, 19 Oct 2015 14:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 YGT6LyTbFt4Z for <ospf@ietfa.amsl.com>; Mon, 19 Oct 2015 14:29:57 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D1881ACE45 for <ospf@ietf.org>; Mon, 19 Oct 2015 14:29:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2428; q=dns/txt; s=iport; t=1445290195; x=1446499795; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=6tBcmYTd9QMSkF/FOolnMHYhGRtZeahZ8g/ay9H2ppo=; b=i6kEDudbmfA+p8wc2aBWJvJOtxLMtPq/FCtd0bTPsDMvP1acPftfk+i4 kuBaT7rSsEuKW55TaHyXhO5OOFCcotxZ0bOqNdp/Zqu+QzrsB9mXtkPIW B3OuFEWDadnpT7cpwzLXyWTenIdlzT8Cg+TzpjHwTdA2GzgwbXjXRr3J1 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D9AQAkYCVW/4oNJK1egzZUbwa+CgENgVoXDIV7AhyBITgUAQEBAQEBAYEKhC4BAQQBAQEgETobAgEIGAICHwcCAgIlCxUQAgQBEhuIFQ2xZpJ9AQEBAQEBAQEBAQEBAQEBAQEBFwSBIopThFoYIoJpgUUFliMBjRyBWIQ8lgMBHwEBQoJEgT9yAYRggQYBAQE
X-IronPort-AV: E=Sophos;i="5.17,704,1437436800"; d="scan'208";a="199459697"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-6.cisco.com with ESMTP; 19 Oct 2015 21:29:54 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t9JLTsZ1019152 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 19 Oct 2015 21:29:54 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 19 Oct 2015 16:29:36 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1104.000; Mon, 19 Oct 2015 16:29:36 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] OSPF Operator-Defined TLVs (https://www.ietf.org/id/draft-chunduri-ospf-operator-defined-tlvs-01.txt)
Thread-Index: AQHRCq9PrW1ep3oWb0OUXrXKrQCznJ5zZiKA
Date: Mon, 19 Oct 2015 21:29:35 +0000
Message-ID: <D24AD7D7.36FA3%acee@cisco.com>
References: <93711831-302C-4D2D-930F-BC76FB554010@ericsson.com>
In-Reply-To: <93711831-302C-4D2D-930F-BC76FB554010@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.199]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7EC5C84DF6F4A6429DB6DC287D61510C@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/jvXHl6iticuOqDoBreSZ4kX6DqE>
Subject: Re: [OSPF] OSPF Operator-Defined TLVs (https://www.ietf.org/id/draft-chunduri-ospf-operator-defined-tlvs-01.txt)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 19 Oct 2015 21:29:58 -0000
Speaking as a WG contributor, I tend to agree as long as one envisions a flooding API for local applications. Hence, I would support this work. I don’t agree with all the use cases as I would think that TE parameters should be standardized. Thanks, Acee On 10/19/15, 4:47 PM, "Jeff Tantsura" <jeff.tantsura@ericsson.com> wrote: >Hi Acee, > >I think the document describes a real and a valid use case, rather useful >when opaque data needs to be distributed in an IGP domain. >Hence support further progress. > >Cheers, >Jeff > > > > > > > >On 10/19/15, 23:29, "OSPF on behalf of Acee Lindem (acee)" ><ospf-bounces@ietf.org on behalf of acee@cisco.com> wrote: > >>This draft has been presented at two IETFs and while I don’t agree with >>some of the proposed use cases as these applications reference should, if >>fact, be standardized, I can see that the use case for local applications >>could be compelling. This is the use where OSPF provides an API for local >>applications to advertise application-specific information throughout the >>routing domain and receive the same parameters from other routers running >>that application. Since this is to support local applications >>generically, >>one could see the reason to allow non-standard parameters to be flooded >>opaquely (i.e., OSPF is used solely as a flooding mechanism). >> >>Please take a look at the draft and indicate whether or not you feel the >>OSPF WG should work on such a solution. If there is enough interest, we >>will adopt it as a WG document. >> >>Thanks, > >Thanks! >>Acee >> >> >> >> >> >>_______________________________________________ >>OSPF mailing list >>OSPF@ietf.org >>https://www.ietf.org/mailman/listinfo/ospf
- [OSPF] OSPF Operator-Defined TLVs (https://www.ie… Acee Lindem (acee)
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Jeff Tantsura
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Acee Lindem (acee)
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Uma Chunduri
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Xuxiaohu
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Acee Lindem (acee)
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Les Ginsberg (ginsberg)
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Xuxiaohu
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… mohamed.boucadair
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… mohamed.boucadair
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Uma Chunduri
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Les Ginsberg (ginsberg)
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… mohamed.boucadair
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Acee Lindem (acee)
- Re: [OSPF] OSPF Operator-Defined TLVs (https://ww… Uma Chunduri