Re: [OSPF] WG adoption poll for draft-ppsenak-ospf-te-link-attr-reuse

"Naiming Shen (naiming)" <naiming@cisco.com> Fri, 07 July 2017 18:20 UTC

Return-Path: <naiming@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 37C4F126DEE for <ospf@ietfa.amsl.com>; Fri, 7 Jul 2017 11:20:52 -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 KnVIjRFpzlLL for <ospf@ietfa.amsl.com>; Fri, 7 Jul 2017 11:20:49 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D63A01317C6 for <ospf@ietf.org>; Fri, 7 Jul 2017 11:20:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5362; q=dns/txt; s=iport; t=1499451645; x=1500661245; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=x8zXFJ3bDq+r5eCgvX/2UMhR7aRzvzniMX9Csu2Bfq0=; b=D7ur9HyuAfXhR0QC2lurMzS6xRC//Z/xvwuFzgduON2oszdj732/gXHa Z8UEC4sjlZ5Sg672nTo8IIXolJ9Uh76fY4FhzWMpT3nXTzLn+dDHi6Ex8 5fQKvOu1Zunc5i7TS5YNScBE5wTjPWyBN4Q6UPK2d9rzporcSUI2qvyGI 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BiAQAk0F9Z/4MNJK1cGwEBAQMBAQEJA?= =?us-ascii?q?QEBg1pkgQETB4NpihmRapYDghEhC4VwAhqDKz8YAQIBAQEBAQEBayiFGAEBAQE?= =?us-ascii?q?CAQEBIRE6CwULAgEIGAICJgICAiULFRACBA4FiicIELAegiaLQwEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARgFgQuCHYVYgkU0hFYUgxMwgjEFlzWHaAKHRoxCggyFS4p?= =?us-ascii?q?JlTkBHziBCnUVSRIBhwN2hmCBMYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.40,324,1496102400"; d="scan'208";a="446824014"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Jul 2017 18:20:44 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v67IKi2I025134 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ospf@ietf.org>; Fri, 7 Jul 2017 18:20:44 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Jul 2017 13:20:44 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Fri, 7 Jul 2017 13:20:44 -0500
From: "Naiming Shen (naiming)" <naiming@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
CC: "Abhay Roy (akr)" <akr@cisco.com>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: [OSPF] WG adoption poll for draft-ppsenak-ospf-te-link-attr-reuse
Thread-Index: AQHS9CuSrW9xjMCpN02i+Fe5nQEhQaJHtLIAgAFB4YCAABBkgA==
Date: Fri, 7 Jul 2017 18:20:44 +0000
Message-ID: <0D82C71D-94CE-4BA4-9CBD-D844B6284A2E@cisco.com>
References: <f50ebb8f-0edd-9fb2-bfdb-f095e613980e@cisco.com> <D5842D5C.B7424%acee@cisco.com> <D5853AE9.B7505%acee@cisco.com>
In-Reply-To: <D5853AE9.B7505%acee@cisco.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.41.50.137]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A565DCA887DFF8408433ED96E1C33255@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/S6Ujf-joHPtvfbt0pf0XdYcWYZU>
Subject: Re: [OSPF] WG adoption poll for draft-ppsenak-ospf-te-link-attr-reuse
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, 07 Jul 2017 18:20:52 -0000

Support the adoption.

- Naiming

> On Jul 7, 2017, at 10:22 AM, Acee Lindem (acee) <acee@cisco.com> wrote:
> 
>                OSPF Evolution and the role of
> draft-ppsenak-ospf-te-link-attr-reuse
> 
> The document draft-ppsenak-ospf-te-link-attr-reuse-05.txt not-only
> provides flexible and compact mechanisms and encodings for advertising
> link attributes for single or multiple applications. It is also part of
> the wider goal of transforming OSPF to a TLV-based protocol that is every
> bit as extendable as the other IGPs while affording the distinct advantage
> of optimally partitioning the advertised information into multiple LSAs of
> different types. 
> 
> This draft represents the last piece of our vision to achieve this
> outcome. For OSPFv2, we have the base LSAs that cannot be extended in a
> backward compatible fashion. Additionally, we have RFC 7770 (OSPF Router
> Information Advertisement) and RFC 7684 (OSPF Prefix/Link Attributes). The
> former has been extended to support distribution of non-OSPF information
> in addition to OSPF Router-level protocol information. The extended OSPF
> Prefix/Link LSAs are being used to support segment routing and other
> technologies. They are now part of the OSPF base and will be advertised in
> many OSPF domains. The major implementations have the capability to
> correlate the base LSAs and the OSPF Prefix/Link LSAs for segment routing.
> This correlation requires handling lots of chicken and egg complexities
> that have all been overcome.
> 
> It has been suggested that since the OSPF TE LSAs (RFC 3630) contain some
> generally useful link attributes, this be the only means by which this
> information is advertised in OSPF routing domains. This will be both
> unwieldy and inefficient due to the advertisement, processing, and storage
> of the TE LSAs in networks not utilizing RSVP-based TE.  There is also the
> added complexity with this approach as you have not only the chicken and
> the egg, but the chicken, egg, and the rooster to correlate.
> 
> For OSPFv3 and OSPFv3 Extended LSAs
> (draft-ietf-ospf-ospfv3-lsa-extend-14.txt), we have made the difficult
> choice to extend the base RFC 5340 LSAs (OSPF for IPv6) in a
> non-compatible fashion. After an initial delay, we have implementations of
> the OSPFv3 Extended LSAs draft and will soon be advancing it. With the
> OSPFv3 extended LSAs, we are finally at the point where all the
> information (other than RSVP TE information) for a given prefix or link is
> advertised in a single LSA rather than multiple LSAs. Would those who
> argue for making OSPFv2 TE LSAs generally applicable also want to require
> the advertisement of RFC 5329 (OSPFv3 Traffic Engineering) LSAs?  If so,
> we would miss a tremendous opportunity.
> 
> 
> Thanks,
> Acee
> 
> On 7/6/17, 6:10 PM, "OSPF on behalf of Acee Lindem (acee)"
> <ospf-bounces@ietf.org on behalf of acee@cisco.com> wrote:
> 
>> Support as co-author. More to come…
>> Acee 
>> 
>> On 7/3/17, 2:37 PM, "OSPF on behalf of Abhay Roy (akr)"
>> <ospf-bounces@ietf.org on behalf of akr@cisco.com> wrote:
>> 
>>> We would like to kick-off a poll for WG adoption of the following
>>> document (per Authors request):
>>> 
>>> https://datatracker.ietf.org/doc/draft-ppsenak-ospf-te-link-attr-reuse
>>> 
>>> Please let us know if you support or have concerns with OSPF WG adopting
>>> this work.
>>> 
>>> Regards,
>>> -Abhay
>>> 
>>> _______________________________________________
>>> 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
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf