IETF Logo Mail Archive

[IPsec] routing protocols for ADVPN

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 06 December 2013 18:41 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5F661ADF22 for <ipsec@ietfa.amsl.com>; Fri, 6 Dec 2013 10:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level:
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_MIME_NO_TEXT=0.01] 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 AtyEv7CJXNiV for <ipsec@ietfa.amsl.com>; Fri, 6 Dec 2013 10:41:44 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC351A1F6F for <ipsec@ietf.org>; Fri, 6 Dec 2013 10:41:44 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 27C9A20050; Fri, 6 Dec 2013 14:55:05 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id E239D63B89; Fri, 6 Dec 2013 13:41:33 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D199463B88; Fri, 6 Dec 2013 13:41:33 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "<ipsec@ietf.org>" <ipsec@ietf.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Fri, 06 Dec 2013 13:41:33 -0500
Message-ID: <19440.1386355293@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "Frederic Detienne (fdetienn)" <fdetienn@cisco.com>
Subject: [IPsec] routing protocols for ADVPN
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2013 18:41:47 -0000

(thread broken intentionally)

Frederic Detienne (fdetienn) <fdetienn@cisco.com> wrote:
    >> ...
    >> - No overlay of additional routing protocols is needed.


    > please note that our proposal does not mandate a routing protocol. We
    > also support IKEv2 config exchange and treat the protected subnets as
    > "routes" for the tunnel. 

I have no idea how to implement what you described.
This is the problem: we have asked questions, and we keep getting "oh, yes,
we can do that", but no actual explanation.

I'd rather that you had mandated OSPFv2/3 or someso that I could evaluate the
entire solution.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email