[OSPF] Suresh Krishnan's Discuss on draft-ietf-ospf-transition-to-ospfv3-10: (with DISCUSS and COMMENT)

"Suresh Krishnan" <suresh.krishnan@ericsson.com> Wed, 29 June 2016 03:41 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ospf@ietf.org
Delivered-To: ospf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 09D7112D5A2; Tue, 28 Jun 2016 20:41:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160629034122.22589.47318.idtracker@ietfa.amsl.com>
Date: Tue, 28 Jun 2016 20:41:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/W7GNp-yWbkfuDrniXdpaxOJpyJA>
Cc: ospf@ietf.org, draft-ietf-ospf-transition-to-ospfv3@ietf.org, ospf-chairs@ietf.org, wenhu.lu@gmail.com
Subject: [OSPF] Suresh Krishnan's Discuss on draft-ietf-ospf-transition-to-ospfv3-10: (with DISCUSS and COMMENT)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 29 Jun 2016 03:41:23 -0000

Suresh Krishnan has entered the following ballot position for
draft-ietf-ospf-transition-to-ospfv3-10: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


I do think this is a good mechanism to transition from IPv4-only OSPFv2
to dual-stack capable OSPFv3 and I intend to switch to a Yes once my
discuss points are addressed. 

* The calculation for the checksum field in the OSPFv3 packet is not
specified in this document. The RFC5340 checksum calculation uses the
IPv6 pseudo-header mechanism for upper layer checksums as specified in
Section 8.1 of RFC2460. Since that obviously won't work here (as there
are no source and dest IPv6 addresses) some different mechanism needs to
be specified here.
* (based on the above) Why doesn't this document update RFC5340?


I do have one question that I am curious about. Can this mechanism be run
alongside OSPFv2 on the same router? If so, how does the demultiplexing
take place to dispatch the packet to either the OSPFv2 or the
OSPFv3-over-IPv4 implementation (as the endpoints are potentially the
same and the IP proto number 89 is usually dispatched to OSPFv2)? Does it
require inserting some sort of shim in the OSPFv2 implementation to
further dispatch on the version number octet?