Re: [OSPF] Jari Arkko's Yes on draft-ietf-ospf-transition-to-ospfv3-11: (with COMMENT)

Jari Arkko <jari.arkko@piuha.net> Thu, 30 June 2016 07:52 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D75B912DA11; Thu, 30 Jun 2016 00:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=no
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 sH_5kgn3hERj; Thu, 30 Jun 2016 00:52:04 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7069712DA09; Thu, 30 Jun 2016 00:52:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9AFBC2CC6F; Thu, 30 Jun 2016 10:52:02 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0oFz6IM7U_EZ; Thu, 30 Jun 2016 10:52:02 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F40422CC64; Thu, 30 Jun 2016 10:52:01 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_80916268-E517-4009-8B4F-5B42AC182B56"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <D317667F-FE8E-4AFA-9C2C-118A50792270@gmail.com>
Date: Thu, 30 Jun 2016 10:52:00 +0300
Message-Id: <ED6562A7-4649-4159-A692-B37F4EE944F1@piuha.net>
References: <20160629221139.30479.45903.idtracker@ietfa.amsl.com> <D317667F-FE8E-4AFA-9C2C-118A50792270@gmail.com>
To: Acee Lindem <acee.lindem@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/rvRr-qz4w9HLkS_7d1dT9a860ho>
Cc: ospf-chairs@ietf.org, OSPF List <ospf@ietf.org>, draft-ietf-ospf-transition-to-ospfv3@ietf.org, The IESG <iesg@ietf.org>, wenhu.lu@gmail.com
Subject: Re: [OSPF] Jari Arkko's Yes on draft-ietf-ospf-transition-to-ospfv3-11: (with COMMENT)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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, 30 Jun 2016 07:52:07 -0000

> I think I see your point. How about:
> 
> As specified in [RFC5340], OSPFv3 relies on IPsec [RFC4301] for
> authentication and confidentiality. [RFC 4552] specifies how IPsec is used
> with OSPFv3 over IPv6 transport. In order to use OSPFv3 with IPv4
> transport as specified herein, further work such as [ipsecospf] would
> be required.

That would be clear. Thanks.

Jari