Re: [OSPF] AD review of draft-ietf-ospf-transition-to-ospfv3-07

"Acee Lindem (acee)" <> Thu, 09 June 2016 23:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0FE6C12D5CB for <>; Thu, 9 Jun 2016 16:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id b7E-oNPpT9SM for <>; Thu, 9 Jun 2016 16:01:50 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DA15812D5A0 for <>; Thu, 9 Jun 2016 16:01:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=18711; q=dns/txt; s=iport; t=1465513309; x=1466722909; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=X6Z9Xu8sq00TP/RihpRtD/dO2/CZRj1fSZ9aMHCHkcw=; b=IcRHQYh00oqOM8pTOyKEBrXa7dgVgX5MOx3c+BtH85mj7bXQ7i8tC7E3 ye/qszDvDdtqdcxYdbw5YECrK754R0KGTypzNO9owIPBMhu43lBvwLYgy A0KItBHxIMaOgPDwByktTHsgA8591SlFyZpmdH13k8bILPXYHWmI/l/pC c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.26,447,1459814400"; d="scan'208,217";a="113496106"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jun 2016 23:01:48 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u59N1m2c025993 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 9 Jun 2016 23:01:48 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 9 Jun 2016 19:01:47 -0400
Received: from ([]) by ([]) with mapi id 15.00.1104.009; Thu, 9 Jun 2016 19:01:47 -0400
From: "Acee Lindem (acee)" <>
To: Alia Atlas <>
Thread-Topic: [OSPF] AD review of draft-ietf-ospf-transition-to-ospfv3-07
Thread-Index: AQHRwok+uUYZzsz18kaAeu9BATV60Z/hu1EAgABHyQD//72bAA==
Date: Thu, 09 Jun 2016 23:01:47 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D37F6D6363F25aceeciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: OSPF List <>
Subject: Re: [OSPF] AD review of draft-ietf-ospf-transition-to-ospfv3-07
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Jun 2016 23:01:52 -0000

Hi Alia,
I agree with your suggestions - we will make update the draft before the tele chat.

From: Alia Atlas <<>>
Date: Thursday, June 9, 2016 at 6:59 PM
To: Acee Lindem <<>>
Cc: OSPF WG List <<>>
Subject: Re: [OSPF] AD review of draft-ietf-ospf-transition-to-ospfv3-07

Hi Acee,

On Thu, Jun 9, 2016 at 6:42 PM, Acee Lindem (acee) <<>> wrote:
Hi Alia,

Thanks for the review - you caught some rather subtle points.

thanks - this was a nice tractable draft to read in a short time.

From: OSPF <<>> on behalf of Alia Atlas <<>>
Date: Thursday, June 9, 2016 at 3:57 PM
To: OSPF WG List <<>>
Subject: [OSPF] AD review of draft-ietf-ospf-transition-to-ospfv3-07

As is customary, I have done my AD review of draft-ietf-ospf-transition-to-ospfv3-07.
First, I would like to thank the authors for their work on this document.  It looks like
very useful technology.

I have a few minor questions below.  I will put this into IETF Last Call as well while
waiting for the authors to update the draft ASAP.   That gives a chance of making it
on to the June 30 telechat if the authors are responsive.


1) Sec 3.1:  "If this is supported, the IPv4 data plane MUST resolve
     the layer-2 address using Address Resolution Protocol (ARP) on
     multi-access networks and point-to-point over LAN [RFC5309] for
     direct next-hops on different IPv4 subnets."

     I believe it is the IPv4 (i.e. layer-3) address to be resolved with ARP - not the
     layer-2 address.

Ok - this text comes from me and I was viewing resolution from the standpoint of the “to” address family rather than the “from” address family. I agree the “from” address family is probably a more common characterization.

Feel free to say "MUST resolve from the IPv4 address to the layer-2 address using ARP...." if you
want extreme clearness.

2) Sec 3.3: "If IPv4 transport, as specified herein, is used for IPv6 address
     families, virtual links cannot be
     supported. Hence, it is RECOMMENDED to use the IP transport
     matching the address family in OSPF routing domains requiring
     virtual links."

     From this section, I was expecting that "cannot" would be a "can".  Did
     I miss something?  Can you clarify further?

The draft doesn’t address virtual link support in deployments where the address-family doesn’t match the transport. Hence, the text is correct as written.

Ok - but the draft  just says
"Hence, it is RECOMMENDED to use the IP transport
     matching the address family in OSPF routing domains requiring
     virtual links."

Can you clean this up to be extremely clear?
With an IPv4 transport, IPv6 virtual links are not supported.
With an IPv4 transport, IPv4 virtual links are supported.

and vice versa.

I read the relaxation as applying to both IPv4 and IPv6; maybe I was reading too fast, but a few clarifying
words would probably help.

3) Sec 1: 2nd to last paragraph: "In situations where the IPv6 deployment is a
   proper superset of the IPv4 deployment, it is expected that OSPFv3
   would be transported over IPv6."

   I believe the "proper" should be removed.   If the IPv6 deployment is exactly the same
   as the IPv4 deployment, then it is expected that OSPFv3 would be transported over
   IPv6.     As it is,how the case of equal deployment is handled is unspecified.

I agree. We will remove “proper".