[OSPF] FW: New Version Notification for draft-ietf-ospf-ospfv3-lsa-extend-08.txt

"Acee Lindem (acee)" <acee@cisco.com> Thu, 08 October 2015 16:56 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 []) by ietfa.amsl.com (Postfix) with ESMTP id A98C91AC3E4 for <ospf@ietfa.amsl.com>; Thu, 8 Oct 2015 09:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Gkm5tXdyh5Zk for <ospf@ietfa.amsl.com>; Thu, 8 Oct 2015 09:56:29 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A9901AC3BF for <ospf@ietf.org>; Thu, 8 Oct 2015 09:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2870; q=dns/txt; s=iport; t=1444323389; x=1445532989; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=3DZ65wi7rYW/4bGefe7VE4fnKr6zwscHsELKo+swm48=; b=Rb7MJWZYIUWKUfjO4v/HtX8q7+J8MRkhho2vpuX7VMRFpXlcs6HBSG7Y uuy+ncseuLrNKzU3w/vCHHdJwd6JkQG6C0tr0TudVWQTXO8Y3tSUYWo+F qsCEVed8F5trZQVwc5rB8IwXR4jFUiqyZt9ynSDxul1RcV9PaJrsXMXqz I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.17,655,1437436800"; d="scan'208";a="33849303"
Received: from alln-core-5.cisco.com ([]) by rcdn-iport-8.cisco.com with ESMTP; 08 Oct 2015 16:56:28 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com []) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t98GuScJ016257 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ospf@ietf.org>; Thu, 8 Oct 2015 16:56:28 GMT
Received: from xch-aln-007.cisco.com ( by XCH-ALN-007.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 8 Oct 2015 11:56:27 -0500
Received: from xhc-rcd-x04.cisco.com ( by xch-aln-007.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Thu, 8 Oct 2015 11:56:27 -0500
Received: from xmb-aln-x06.cisco.com ([]) by xhc-rcd-x04.cisco.com ([]) with mapi id 14.03.0248.002; Thu, 8 Oct 2015 11:56:27 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: OSPF WG List <ospf@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-ospf-ospfv3-lsa-extend-08.txt
Thread-Index: AQHRAelxJZ9jfsGOlkmaSltmu1DUfZ5h4YgA
Date: Thu, 8 Oct 2015 16:56:26 +0000
Message-ID: <D23C173E.342D0%acee@cisco.com>
References: <20151008165017.5438.82525.idtracker@ietfa.amsl.com>
In-Reply-To: <20151008165017.5438.82525.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <C6C54377FB386243B95EBB8F240DEE93@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/XxbAfohRVV5sd5LLmkkWD83lP_o>
Subject: [OSPF] FW: New Version Notification for draft-ietf-ospf-ospfv3-lsa-extend-08.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: Thu, 08 Oct 2015 16:56:30 -0000

Since we’ve gone for over two years without significant implementation
traction, I’ve added the “sparse-mode” of backward compatibility where the
OSPFv3 Extended-LSAs MAY only originated as needed for new functions and
backward compatibility is dependent solely on the limitations of those
functions. Please take a look - this is analogous to the direction taken
for OSPFv2 in 


On 10/8/15, 12:50 PM, "internet-drafts@ietf.org"
<internet-drafts@ietf.org> wrote:

>A new version of I-D, draft-ietf-ospf-ospfv3-lsa-extend-08.txt
>has been successfully submitted by Acee Lindem and posted to the
>IETF repository.
>Name:		draft-ietf-ospf-ospfv3-lsa-extend
>Revision:	08
>Title:		OSPFv3 LSA Extendibility
>Document date:	2015-10-08
>Group:		ospf
>Pages:		34
>   OSPFv3 requires functional extension beyond what can readily be done
>   with the fixed-format Link State Advertisement (LSA) as described in
>   RFC 5340.  Without LSA extension, attributes associated with OSPFv3
>   links and advertised IPv6 prefixes must be advertised in separate
>   LSAs and correlated to the fixed-format LSAs.  This document extends
>   the LSA format by encoding the existing OSPFv3 LSA information in
>   Type-Length-Value (TLV) tuples and allowing advertisement of
>   additional information with additional TLVs.  Backward compatibility
>   mechanisms are also described.
>Please note that it may take a couple of minutes from the time of
>until the htmlized version and diff are available at tools.ietf.org.
>The IETF Secretariat