[OSPF] Rtgdir early review of draft-ietf-ospf-ospfv3-lsa-extend-14

Min Ye <amy.yemin@huawei.com> Wed, 17 May 2017 09:22 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Min Ye <amy.yemin@huawei.com>
To: rtg-dir@ietf.org
Cc: ospf@ietf.org, ietf@ietf.org, draft-ietf-ospf-ospfv3-lsa-extend.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149501293882.6715.9441857001639471954@ietfa.amsl.com>
Date: Wed, 17 May 2017 02:22:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/RulzH96lq5UlrTR6z3HSUfY1Txk>
Subject: [OSPF] Rtgdir early review of draft-ietf-ospf-ospfv3-lsa-extend-14

Reviewer: IJsbrand Wijnands
Review result: Has Issues

Hi All,

I have been selected to do a routing directorate QA review of this
draft.
https://www.ietf.org/id/draft-ietf-ospf-ospfv3-lsa-extend-14.txt

Summary: 

This draft proposes a new addressing (TLV) format to more easily allow

additional information to be added as part of a particular LSA. 
Overall, well written, easy to understand what the objective is for
this draft.

Comments and Questions:

This looks like a pretty radical change to the OSPFv3 spec. I would 
almost argue to call it OSPFv4..

Its very unfortunate there are no ‘reserved’ fields in RFC5340 that 
would allow you keep the existing LSA’s format and have some way to 
extend it differently. The TLV approach look good, I can’t see a
better 
way to achieve the goal.

Minor Issues and Nits:
none.

Thx,

Ice.

[OSPF] Rtgdir early review of draft-ietf-ospf-osp… Min Ye
Re: [OSPF] Rtgdir early review of draft-ietf-ospf… Acee Lindem (acee)
Re: [OSPF] Rtgdir early review of draft-ietf-ospf… Yemin (Amy)