Re: [netext] pmip-cp-up-separation
"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Fri, 16 August 2013 15:59 UTC
Return-Path: <sgundave@cisco.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E028711E82A4 for <netext@ietfa.amsl.com>; Fri, 16 Aug 2013 08:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id svM46kMiZxUp for <netext@ietfa.amsl.com>; Fri, 16 Aug 2013 08:59:45 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id D3BFA21F9C4A for <netext@ietf.org>; Fri, 16 Aug 2013 08:59:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7657; q=dns/txt; s=iport; t=1376668785; x=1377878385; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=5BCRtbfj3Cr1X3P7PuziWXYyidfspIX9R4VlbP6PhHw=; b=Xe7z9kbU6S8cqp9+K3gdWAwLgdU/UqcLlmEzTyTB6F7nm16GlqzBIoWt uoIExEut1pRs6jLliNFLNvMTQLb/fMhGPYxjmq+Wei8pATSW+rm58FHjG AmWsNOB8XkGcwiYbzO2ia2D4Xv7Pai9cgXX1ZyOfx/qcTGalQCo30zsOR s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFANtLDlKtJXG+/2dsb2JhbABSCYJCRIEGvx+BKxZ0giQBAQEEZyQBCBEDAQILHTkUCQgCBAESCIgIuhaPCoEVIBiDG3cDqTmDHIIq
X-IronPort-AV: E=Sophos; i="4.89,895,1367971200"; d="scan'208,217"; a="248198246"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-6.cisco.com with ESMTP; 16 Aug 2013 15:59:44 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r7GFxhXX016952 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 16 Aug 2013 15:59:43 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.31]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Fri, 16 Aug 2013 10:59:43 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Alper Yegin <alper.yegin@yegin.org>, "netext@ietf.org" <netext@ietf.org>
Thread-Topic: [netext] pmip-cp-up-separation
Thread-Index: AQHOmpmeRDMx9JXmgESNpc+6UBD3EQ==
Date: Fri, 16 Aug 2013 15:59:42 +0000
Message-ID: <24C0F3E22276D9438D6F366EB89FAEA8103FFF1A@xmb-aln-x03.cisco.com>
In-Reply-To: <24C0F3E22276D9438D6F366EB89FAEA8103FFEE2@xmb-aln-x03.cisco.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.210]
Content-Type: multipart/alternative; boundary="_000_24C0F3E22276D9438D6F366EB89FAEA8103FFF1Axmbalnx03ciscoc_"
MIME-Version: 1.0
Subject: Re: [netext] pmip-cp-up-separation
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 16 Aug 2013 15:59:51 -0000
Also, if I see the use-cases from Ryuji, his interest is for dynamic DP allocation. Sri From: Sri Gundavelli <sgundave@cisco.com<mailto:sgundave@cisco.com>> Date: Friday, August 16, 2013 8:57 AM To: Alper Yegin <alper.yegin@yegin.org<mailto:alper.yegin@yegin.org>>, "netext@ietf.org<mailto:netext@ietf.org>" <netext@ietf.org<mailto:netext@ietf.org>> Subject: Re: [netext] pmip-cp-up-separation Hi Alper, We were thinking of allowing the option to be carried in the PBU with 0.0.0.0/0::0 to indicate capability and also to keep it aligned with the other mobility options that we have defined recently. So, in that sense the option may be present in the PBU, but I'm wondering in what cases, the MAG would have more specific information. In general, the LMA-CP identity may be known to the MAG, but may be not the DP identity; there the broader goal is to have the DP identity be dynamically allocated by LMA-CP and have that exposed to the MAG as part of the signaling exchange. Regards Sri From: Alper Yegin <alper.yegin@yegin.org<mailto:alper.yegin@yegin.org>> Date: Friday, August 16, 2013 6:19 AM To: "netext@ietf.org<mailto:netext@ietf.org>" <netext@ietf.org<mailto:netext@ietf.org>> Subject: [netext] pmip-cp-up-separation LMA User Plane Address Mobility Option is only used with the PBA. If the MAG has prior info about the LMA-UPA, it could also provide that in PBU. Should we allow that new option with PBU as well? Alper
- [netext] NETEXT session recording available Meetecho IETF support
- [netext] NETEXT session recording available Meetecho Team
- [netext] pmip-cp-up-separation Alper Yegin
- Re: [netext] pmip-cp-up-separation Sri Gundavelli (sgundave)
- Re: [netext] pmip-cp-up-separation Sri Gundavelli (sgundave)