Re: [OSPF] FW: New Version Notification for draft-ietf-ospf-ospfv3-lsa-extend-02.txt
Acee Lindem <acee.lindem@ericsson.com> Fri, 18 April 2014 16:22 UTC
Return-Path: <acee.lindem@ericsson.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 AFA981A0279 for <ospf@ietfa.amsl.com>; Fri, 18 Apr 2014 09:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 wRP2C71S6BWZ for <ospf@ietfa.amsl.com>; Fri, 18 Apr 2014 09:22:41 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8A71A013F for <ospf@ietf.org>; Fri, 18 Apr 2014 09:22:41 -0700 (PDT)
X-AuditID: c618062d-f79f66d000001393-bb-535102dac389
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 22.FE.05011.AD201535; Fri, 18 Apr 2014 12:47:55 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0174.001; Fri, 18 Apr 2014 12:22:36 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Peter Psenak <ppsenak@cisco.com>
Thread-Topic: [OSPF] FW: New Version Notification for draft-ietf-ospf-ospfv3-lsa-extend-02.txt
Thread-Index: AQHPWxvzDq21FEGbJU2CC2V6eH593ZsXVa8AgAB6rwCAAAFJAA==
Date: Fri, 18 Apr 2014 16:22:36 +0000
Message-ID: <54238B77-60C7-4392-B396-A5B6B43B31BC@ericsson.com>
References: <20140418153616.2339.51730.idtracker@ietfa.amsl.com> <CF7698CD.2C967%acee.lindem@ericsson.com> <53515038.9070407@cisco.com>
In-Reply-To: <53515038.9070407@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2D9164AFB4969143AF0105DD52EEFC95@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyuXRPgu5tpsBgg4/bGC1a7t1jt9ixu53N gcljyu+NrB5LlvxkCmCK4rJJSc3JLEst0rdL4MqY3LWFtWCWZEXf/EdsDYzPRLoYOTkkBEwk zs1bzQhhi0lcuLeerYuRi0NI4CijxN/j11ghnOWMEieWrGAFqWIT0JF4/ugfM4gtIqAiMe96 DwuIzSwgK/FsWxNYXFggXuJI+wd2iJoEiR17frJC2E4S05vngNWwCKhKnLmzgg3E5hWwl5h6 9B4TxLJORombrS/BGjgFNCWW/54LZjMCnff91BomiGXiEreezGeCOFtAYsme88wQtqjEy8f/ WCFsJYmPv+ezQ9QbSLw/Nx+ohgPItpa4+tcJIqwtsWzha2aIGwQlTs58wjKBUXwWkg2zkHTP QuiehaR7FpLuBYysqxg5SotTy3LTjQw2MQKj6pgEm+4Oxj0vLQ8xCnAwKvHwTrnuGyzEmlhW XJl7iFGag0VJnPfLW+cgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxlYs/+PjsazXvzvaxT jfyZzjtSdjIy5UdyDjv6zZzAdGTm9+wHv/6XhuTufPVo2cK6BQ2mOzIXTOy77XKj8NUbJ0al B0EqS9+GzFvTXOD186xP1fy0HY3Tp7yYwD53I//nq3l5/15kXMw/ejckZS/PrGIfy1OSu5/v Mry34MvlC+8idkinnUu8qsRSnJFoqMVcVJwIACkoIMuLAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/GroBt5RAALsBl5L_WAJpGelXtog
Cc: OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] FW: New Version Notification for draft-ietf-ospf-ospfv3-lsa-extend-02.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: <http://www.ietf.org/mail-archive/web/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, 18 Apr 2014 16:22:51 -0000
Hi Peter, You are correct - I’d thought about these situations myself but didn’t strike this statement. I’m thinking I will remove this and discuss the options of separate routing domains in more detail. Thanks, Acee On Apr 18, 2014, at 12:18 PM, Peter Psenak <ppsenak@cisco.com> wrote: > Hi Acee, > > quote From section (5): > > "In this manner, OSPFv3 routers using new encodings can be > completely isolated from those OSPFv3 routers depending on the RFC > 5340 encoding and not setting their options field EL-bits since the > default setting indicates no support for extended LSAs." > > Even though you prevent adjacency to be formed between routers with certain compatibility modes, it still does not prevent all modes to coexist in the area/network. > > Let's imagine you have a chain of routers with following modes: > > Full---MixedModeOriginateSPF----MixedModeOriginateOnly-----None > > > thanks, > Peter > > On 4/18/14 17:58 , Acee Lindem wrote: >> All, >> This version has been reorganized to separate the definitions of the TLVs >> and sub-TLVs from the Extended LSAs (Alan Davey's suggestion). >> It also includes the changes to the compatibility section discussed during >> the OSPF WG meeting in London (David Lamparter's input). >> Thanks, >> Acee >> >> On 4/18/14 8:36 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org> >> wrote: >> >>> >>> A new version of I-D, draft-ietf-ospf-ospfv3-lsa-extend-02.txt >>> has been successfully submitted by Acee Lindem and posted to the >>> IETF repository. >>> >>> Name: draft-ietf-ospf-ospfv3-lsa-extend >>> Revision: 02 >>> Title: OSPFv3 LSA Extendibility >>> Document date: 2014-04-18 >>> Group: ospf >>> Pages: 35 >>> URL: >>> http://www.ietf.org/internet-drafts/draft-ietf-ospf-ospfv3-lsa-extend-02.t >>> xt >>> Status: >>> https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-lsa-extend/ >>> Htmlized: >>> http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-lsa-extend-02 >>> Diff: >>> http://www.ietf.org/rfcdiff?url2=draft-ietf-ospf-ospfv3-lsa-extend-02 >>> >>> Abstract: >>> 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 >>> submission >>> until the htmlized version and diff are available at tools.ietf.org. >>> >>> The IETF Secretariat >>> >> >> _______________________________________________ >> OSPF mailing list >> OSPF@ietf.org >> https://www.ietf.org/mailman/listinfo/ospf >> >
- [OSPF] FW: New Version Notification for draft-iet… Acee Lindem
- Re: [OSPF] FW: New Version Notification for draft… Peter Psenak
- Re: [OSPF] FW: New Version Notification for draft… Acee Lindem
- Re: [OSPF] FW: New Version Notification for draft… Peter Psenak
- Re: [OSPF] New Version Notification for draft-iet… Acee Lindem
- Re: [OSPF] New Version Notification for draft-iet… Acee Lindem
- Re: [OSPF] New Version Notification for draft-iet… Acee Lindem