IETF Logo Mail Archive

Re: 6man-sadr-overview - next-hop option and VPN use-case clarifications

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 23 March 2015 19:29 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B5461B29A6 for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2015 12:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 P6mbhiqJTZ58 for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2015 12:29:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 200D91B29A5 for <ipv6@ietf.org>; Mon, 23 Mar 2015 12:29:20 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 61A92203BD for <ipv6@ietf.org>; Mon, 23 Mar 2015 15:39:07 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 648CB63B76; Mon, 23 Mar 2015 15:29:19 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4AA72636A2 for <ipv6@ietf.org>; Mon, 23 Mar 2015 15:29:19 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 6man WG <ipv6@ietf.org>
Subject: Re: 6man-sadr-overview - next-hop option and VPN use-case clarifications
In-Reply-To: <109399D7-3355-4E6F-83E0-E41FC6F8DAB3@employees.org>
References: <882C9301-A72A-464A-9DE0-D845316EF217@darou.fr> <551057E4.9020008@gmail.com> <109399D7-3355-4E6F-83E0-E41FC6F8DAB3@employees.org>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
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: Mon, 23 Mar 2015 15:29:19 -0400
Message-ID: <8290.1427138959@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ATaREBj8dBEn-JBij8MYLbvxu2E>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 19:29:22 -0000

Ole Troan <otroan@employees.org> wrote:
    >> The reason this *matters* is that whenever a prefix is added or removed
    >> inside the corporate network, the list of host routes built into
    >> the VPN client becomes obsolete and needs to be updated on every
    >> host where that client is installed. That is painful for everyone
    >> involved.

    > the confusion here is why router A needs to advertise to a host that
    > prefix X is reachable via router B, interface Y. 
    > why can’t router B do that.

In the IPv4, non-SADR case, we need this so that the VPN traffic can get to
the VPN end-point.  The VPN clients knows this, and it doesn't need to be
told.  Given SADR, we don't need this.

But, maybe we are not understanding what is really being proposed.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email