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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Sat, 09 August 2014 16:54 UTC

Return-Path: <sgundave@cisco.com>
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 5D4981A004E; Sat, 9 Aug 2014 09:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.469
X-Spam-Level:
X-Spam-Status: No, score=-12.469 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 B7lT19t0XZnE; Sat, 9 Aug 2014 09:54:35 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A07D01A0033; Sat, 9 Aug 2014 09:54:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3097; q=dns/txt; s=iport; t=1407603276; x=1408812876; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=CFhwCJyFZHy7CIFtTwOLLLmBf0Q1C2FRHibzZKTB+sM=; b=A6mLd294AEP7SJST7ys3/daEfDCvZhPSvScMX668CehpSOmO1HWUY465 44AEXam+uwzc1xQuqucCx4glqrF64ONhhyAU/SzvNYPjeIWBQgy0nXEXq /Y24znw5LXDqkiQhayeQE8xpAilBRLIJu/Ng74kc//uINaGYmpU7nUHPS U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAMdR5lOtJA2H/2dsb2JhbABYgw1SW80NCoZ1UwGBCBZ3hAQBAQQBAQE3NAsSAQg2BTILJQIEAQ0FiEINxQUTBIwdgnwzB4RMBYYPiwqLFowBiHqCFoFGbIFH
X-IronPort-AV: E=Sophos;i="5.01,833,1400025600"; d="scan'208";a="343203885"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-9.cisco.com with ESMTP; 09 Aug 2014 16:54:35 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s79GsYFJ001822 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 9 Aug 2014 16:54:34 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.251]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Sat, 9 Aug 2014 11:54:34 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Thread-Topic: [netext] Stephen Farrell's Discuss on draft-ietf-netext-pmip-cp-up-separation-05: (with DISCUSS and COMMENT)
Thread-Index: AQHPs/KYPGye9+SND0qnD+DkG+NETQ==
Date: Sat, 09 Aug 2014 16:54:34 +0000
Message-ID: <D00AAFE7.157466%sgundave@cisco.com>
In-Reply-To: <20140807125031.22597.56137.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.32.246.222]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28B815A64E812649AF84BBC894D12564@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/netext/faHa2V27CjufcU0lHCWtNkHMx7w
Cc: "netext@ietf.org" <netext@ietf.org>, "netext-chairs@tools.ietf.org" <netext-chairs@tools.ietf.org>, "draft-ietf-netext-pmip-cp-up-separation@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: Sat, 09 Aug 2014 16:54:38 -0000

Hi Stephen,

Thanks for the review. Please see inline.



On 8/7/14 5:50 AM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

>
>I have two questions. They could be easy or hard, I'm not
>sure:-) Apologies in advance if I've forgotten what little I
>ever knew about PMIPv6 and gotten stuff wrong here.

Not at all. Thanks for the discussion.

>
>(1) PMIPv6 traffic between MAG and LMA is generally assumed to
>be protected via IPsec, right? Assuming that's actually done,
>does figure 1 here indicate a weakening of security since it
>shows that IP encapsulation is used between MAG-UP and LMA-UP
>without any mention of IPsec. Is that downgrading security? I
>get that the binding messages are the most important and will
>presumably continue on the control plane but what else changes?

Yes. PMIPv6 allows the use of IPsec security (Tunnel Mode ESP) protection
for the user-plane traffic. This is optional and is based on standard
IPsec security. It requires no special interaction between IPsec and the
Proxy Mobile IPv6 entities.

In the split mode (LMA ==> LMA-CP & LMA-DP), the MAG (or MAG-DP) and the
LMA-DP can optionally enable IPsec security on the user-plane traffic.
MAG-DP establishes a layer-3 p2p tunnel to LMA-DP and both these peers can
be configured to apply IPsec security on the tunneled traffic. So, there
is no loss of functionality here and the CP/DP split approach is not
resulting in weakened security.



>
>(2) How does the rest of the Internet know to use the LMA-UP
>for the MN and not the LMA-CP? Sorry for being dense but I
>don't see how packets from a random Internet node for the MN
>end up going down the user plane.

The IP address of the mobile node is topologically anchored on the LMA-DP.
>From the point of view of Routing, the LMA-DP owns that larger IP prefix
block from which it allocates to IP prefixes/address to individual
mobility sessions. The LMA-DP is in the path for the user-plane traffic
and is the entry point into the mobile network.  However, the LMA-CP is
only terminating the control signaling from the MAG and is not in the path
for the user-plane traffic.


 

>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>
>Did you need to say somewhere which PMIPv6 messages are to be
>sent in the control plane and which in the user plane? That
>might be obvious to some, but its not to me and I guess there
>are a bunch of PMIPv6 extensions so I could imagine that
>someone somewhere might get it wrong.
>


The signaling messages {IPv6 with Mobility Header, or IPv4 UDP Port 5436)
traffic is exchanged between MAG-CP and LMA-CP. There is no implication on
the use/non-use of other mobility options.

The tunneled traffic with L3 encapsulation is between MAG-DP and LMA-DP.


Regards
Sri







>
>_______________________________________________
>netext mailing list
>netext@ietf.org
>https://www.ietf.org/mailman/listinfo/netext