Re: [DMM] Two new drafts

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Tue, 09 July 2013 19:45 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4859611E813A for <dmm@ietfa.amsl.com>; Tue, 9 Jul 2013 12:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 yhCzjuxmOLtY for <dmm@ietfa.amsl.com>; Tue, 9 Jul 2013 12:45:52 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id AA86211E8145 for <dmm@ietf.org>; Tue, 9 Jul 2013 12:45:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3135; q=dns/txt; s=iport; t=1373399152; x=1374608752; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=oBtg62AgXFzug/ouvbEmcsZMh+fKYXYIyGWFKslaQmo=; b=mXiximpmxujmrfuY2RGIpmh07h25/pBdIidNRobzv9YnIFq6egBx33Ih V6huvBEuhG9dcbdmqxmqI3eGZzDPpeepLe08yD1c5MPZ3pBPKgKt99WyC PgYz/stUGkbgIHTDy1RzUuDq+zPx969FfIOmCs66SDq2U33hmWqMiiJj4 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFABRo3FGtJXHA/2dsb2JhbABbFoJzMk3BEIEaFnSCIwEBAQQBAQFrCwwGAQgRBAEBAQodLgsUCQgCBA4FCAESh3QMuXuPOjEHBoMDawOYfZAggxGCKA
X-IronPort-AV: E=Sophos;i="4.87,1029,1363132800"; d="scan'208";a="232785620"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-3.cisco.com with ESMTP; 09 Jul 2013 19:45:52 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r69JjpWA014942 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Jul 2013 19:45:52 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.173]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Tue, 9 Jul 2013 14:45:51 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Seil Jeon <seiljeon@av.it.pt>
Thread-Topic: [DMM] Two new drafts
Thread-Index: AQHOfNzqcBpPAutMk0mWcj9nsZrcaw==
Date: Tue, 09 Jul 2013 19:45:51 +0000
Message-ID: <24C0F3E22276D9438D6F366EB89FAEA81032CE4E@xmb-aln-x03.cisco.com>
In-Reply-To: <002501ce7c8b$7b532cf0$71f986d0$@av.it.pt>
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.213]
Content-Type: text/plain; charset="iso-8859-2"
Content-ID: <2169411AB97C4F49B3934C39B1ADC6DB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [DMM] Two new drafts
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 19:45:57 -0000

Hi Seil,

In one abstraction, that middleware is the socket layer performing address
binding. The key point is that we need to add additional meta-data to a
prefix and carry them in ND/DHCP from the network to the host. So, the
host has awareness on different types of IP addresses for use and with the
corresponding properties. This helps in DMM solution, also for supporting
SIPTO in WLAN-EPC integrated solutions. We don't have to deal with monster
NAT's in case of IPv6-based flow offload.



Regards
Sri




 

On 7/9/13 3:02 AM, "Seil Jeon" <seiljeon@av.it.pt> wrote:

>Hi Sri,
>
>Picking source address by an application would be the right way to go?
>I've
>known that's the work of the middleware.
>The middleware needs to be aware of the applications and thus to act
>properly.
>
>Regards
>Seil
>
>-----Original Message-----
>From: dmm-bounces@ietf.org [mailto:dmm-bounces@ietf.org] On Behalf Of Sri
>Gundavelli (sgundave)
>Sent: Tuesday, July 09, 2013 6:23 AM
>To: Alper Yegin; dmm@ietf.org
>Subject: Re: [DMM] Two new drafts
>
>Hi Alper,
>
>Thanks for sharing the documents.
>
>I did a quick review of the dmm-ondemand draft. This is inline with my
>thinking as well. IMO, the following base semantics will allow us to
>realize
>some of the DMM deployment models.
>
>- Prefix Coloring/ Coloring of IP addresses based on the properties
>
>- Delivering the properties as meta-data in address assignment procedures
>(ND, DHCP ..)
>- Evolving the source address selection Rules, allowing application to
>pick
>source address based on the requirements
>
>With these semantics, a UE can obtain multiple IP addresses with different
>properties, bind applications to those addresses based on the application
>requirements, roam within the network loosing some local addresses and
>generating some new ones ...
> 
>
>Slides from 2010 I think ..?
>
>http://www.psg.com/~charliep/txt/ietf81/alt_mext/Evolving-The-SAS-Rules-fo
>r
>-Mobility-Awareness-2.pdf
>
>
>Good to see this. Hope we make progress on these base work such as prefix
>coloring Å which are the enablers ..
>
>http://www.ietf.org/id/draft-korhonen-6man-prefix-properties-01.txt
>http://datatracker.ietf.org/doc/draft-bhandari-dhc-class-based-prefix/
>
>
>Your proposal can leverage the above work.
>
>
>
>Regards
>Sri
>
>
>
>
>
>
>
>On 7/8/13 8:30 AM, "Alper Yegin" <alper.yegin@yegin.org> wrote:
>
>>Hello dear DMM folks,
>>
>>We published the following two new drafts which relate to the DMM WG.
>>
>>http://www.ietf.org/id/draft-yegin-dmm-cnet-homing-00.txt
>>
>>http://www.ietf.org/id/draft-yegin-dmm-ondemand-mobility-00.txt
>>
>>We'd appreciate if you can read and share your comments.
>>
>>(Related IPR statements will be posted on the IETF site soon)
>>
>>Cheers,
>>
>>Alper
>>
>>
>>_______________________________________________
>>dmm mailing list
>>dmm@ietf.org
>>https://www.ietf.org/mailman/listinfo/dmm
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm
>