Re: [netext] Stephen Farrell's Discuss on draft-ietf-netext-pmip-cp-up-separation-05: (with DISCUSS and COMMENT)

Brian Haberman <brian@innovationslab.net> Thu, 28 August 2014 12:02 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238EB1A038A; Thu, 28 Aug 2014 05:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 fVWLDbRRVy_3; Thu, 28 Aug 2014 05:02:56 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 440291A038B; Thu, 28 Aug 2014 05:02:54 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 22CA2880E5; Thu, 28 Aug 2014 05:02:54 -0700 (PDT)
Received: from 1025210111.rude2.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 2982671B0001; Thu, 28 Aug 2014 05:02:53 -0700 (PDT)
Message-ID: <53FF1A6C.5060602@innovationslab.net>
Date: Thu, 28 Aug 2014 08:02:52 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Charlie Perkins <charles.perkins@earthlink.net>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
References: <D023CBF3.15BFFF%sgundave@cisco.com> <53FEB333.3090108@earthlink.net>
In-Reply-To: <53FEB333.3090108@earthlink.net>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="XBSHtft5LwHbb23g6Q2dFp92pvhcHDTwr"
Archived-At: http://mailarchive.ietf.org/arch/msg/netext/3iIO2xbZRazsJdNIUdCbXhDq__s
Cc: netext@ietf.org, netext-chairs@tools.ietf.org, draft-ietf-netext-pmip-cp-up-separation@tools.ietf.org
Subject: Re: [netext] Stephen Farrell's Discuss on draft-ietf-netext-pmip-cp-up-separation-05: (with DISCUSS and COMMENT)
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext/>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 12:02:59 -0000

Hi Charlie,

On 8/28/14 12:42 AM, Charlie Perkins wrote:
> 
> Hello folks,
> 
> I am basically O.K. with the suggested.  A couple of minor points:
> 
> - "any standard security negotiation protocols" -- should this be
> restricted to IETF
>     protocols?  What is the difference between a "security negotiation
> protocol"
>     and a "security protocol"?  Shouldn't we allow static configuration
> in some
>     circumstances for some installations?
> 
> - "make the use of IPsec as optional"  -->  "does not require the use of
> IPsec"
>         or, maybe, "specifies that the use of IPsec is optional"
> 
> Is it the consensus of those involved here that this change does not
> require
> input from the working group?

Not at all, that is why the WG mailing list is copied on these
discussions.  As the shepherding AD, I want to make sure that the
discussion with the dissenting AD is resolved.  If WG members disagree
with the proposed changes, they are free to raise that disagreement.  If
the resulting changes are substantive, I will ask the chairs to review
those changes with the WG prior to any publication approval.

Regards,
Brian