Re: [IPsec] Some comments / questions on draft-ietf-ipsecme-ad-vpn-problem

Vishwas Manral <vishwas.ietf@gmail.com> Thu, 06 December 2012 18:55 UTC

Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7693921F8813 for <ipsec@ietfa.amsl.com>; Thu, 6 Dec 2012 10:55:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level:
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JpaHYRgC8H1e for <ipsec@ietfa.amsl.com>; Thu, 6 Dec 2012 10:55:47 -0800 (PST)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id CEA4B21F8803 for <ipsec@ietf.org>; Thu, 6 Dec 2012 10:55:46 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id i20so871104qad.10 for <ipsec@ietf.org>; Thu, 06 Dec 2012 10:55:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hhmHZpdYlWUfFQ1R2jZnmKRQX+kVSR+MJcDixZ28EgY=; b=W+deEIZYHnYtME6S1TJsHmpeU+0Y2hNk5L96z6KjD0had9RbrJDv3k1QvdHMx853PB 4pApmBaTEaCuP6vJqo3mCrhzWH03/nojrLhgt6rd+0GaZQgeN3FA+77/HRP6yvo4XE5U ocd5/fT6+IY6W0oa/NPp5kX82SaDOQz7QWFCEQ/AQ2IH8RY2mLef23yIp+vgP+Z+Y+Is RyC8WlwDGkE1BXSTR8yYSCJ/Qh5iSRztyh3VQytgIk+3mxLD8zi1Igwzpe8MmEBOWB/i KSiu/SfZJagQtHIDNoUH/vv64BffYyIiUnmq4xagXYJCOmK+g2+kOP5rGevUuRPymYUw U+Vw==
MIME-Version: 1.0
Received: by 10.229.38.35 with SMTP id z35mr923923qcd.144.1354820146262; Thu, 06 Dec 2012 10:55:46 -0800 (PST)
Received: by 10.229.92.77 with HTTP; Thu, 6 Dec 2012 10:55:46 -0800 (PST)
In-Reply-To: <50BFCA9A.4030502@labn.net>
References: <50A5703F.4070305@labn.net> <CAOyVPHTWhv8=sP6kYkZmOEsjMsdr72P8fe=7w5XY0Hd_wP_9=w@mail.gmail.com> <50A58CDB.30402@labn.net> <CAOyVPHQ+n83DaVv6Q9Z0kvi0MyYrhPbB=L6ju4fwjTyRK1P22Q@mail.gmail.com> <50A682F8.9080907@labn.net> <CAOyVPHSvWhgaYm2s_8_37VuaR1e_5tiJai+04AKzm3HXkNwESg@mail.gmail.com> <50A689A9.1090803@labn.net> <CAOyVPHR1euA9TRnAp7V+OKjRkPARYYvQ+C0HnA70y-122sy9ZQ@mail.gmail.com> <50A68D30.2040203@labn.net> <CAOyVPHR4OVNuvMU-UxZAJUoKFugCWwUQq0dSRo-7gY=Y886LoQ@mail.gmail.com> <CAOyVPHRopwvE5U3ZF7kDxNe59OgTk7ydoFG6iqvZdOFUCvaGyA@mail.gmail.com> <50BE30D9.4030903@labn.net> <CAOyVPHSXQQt_31Y2MP+iMe8d0MCxSyKzVvCLL-HLkcggaOKuMw@mail.gmail.com> <50BE4A60.1000303@labn.net> <CAOyVPHSkGVvGD2bMgk-vp3DO0o9N9Zt6mf4SnaL4L9ZFR8NRHg@mail.gmail.com> <50BFA4C0.1060909@labn.net> <CAOyVPHQu+NyQvxMjHJ0=0YtrH6rerU-etEmqQKTKP4jt4sHZgw@mail.gmail.com> <50BFCA9A.4030502@labn.net>
Date: Thu, 06 Dec 2012 10:55:46 -0800
Message-ID: <CAOyVPHQyVz0jCAFGdqLpCxE2tm5TBCkEXKLPBxigQasw=wNW9Q@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary="0016369205048d735f04d033a57b"
Cc: IPsecme WG <ipsec@ietf.org>
Subject: Re: [IPsec] Some comments / questions on draft-ietf-ipsecme-ad-vpn-problem
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Dec 2012 18:55:47 -0000

Hi Lou,

I have included the other comments. The last one remaining is:

> VM> I think this is an important requirement. A tunnel should be able to
> > provide an interface by which when tunnel IP parameters change we do not
> > have to change any configuration for higher application like Routing. I
> > had earlier mentioned in more generic terms earlier but changed to the
> > terms provided based on feedback from the list.
>
> What higher level protocols like most routing protocols that use the
> tunnel interface IP addresses in operation?
>
> >
> > The entire idea is the with scale configuration needs to be reduced and
> > that needs to happen across layers, so every layer needs to provide the
> > service. Let me know what it is I am unable to convey.
>
> sure, but I think you're placing new requirements on the routing &
> tunneling protocols.
>
> VM> There are no restrictions on an application protocol like Routing. The
idea is that the lower needs to provide a functionality, so that if
required a higher layer can use it. There is no restriction at all on the
higher layer. Do let me know if that is clearer?

Thanks,
Vishwas