
From jxyswallow@gmail.com  Wed Dec  9 04:39:03 2009
Return-Path: <jxyswallow@gmail.com>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 854283A690A for <netext@core3.amsl.com>; Wed,  9 Dec 2009 04:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DRB6BfdFma-l for <netext@core3.amsl.com>; Wed,  9 Dec 2009 04:39:02 -0800 (PST)
Received: from mail-px0-f177.google.com (mail-px0-f177.google.com [209.85.216.177]) by core3.amsl.com (Postfix) with ESMTP id A93FC3A6892 for <netext@ietf.org>; Wed,  9 Dec 2009 04:39:02 -0800 (PST)
Received: by pxi7 with SMTP id 7so785322pxi.31 for <netext@ietf.org>; Wed, 09 Dec 2009 04:38:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=31hQ7xi0ZA5OrdyTIBeD5E/8WJMqUQgWEq7/8K7NBPU=; b=O8WayBnI/dhqVgEMQfy9JBCqmESOEzYyjruQQ7vECp/E/UzPafHDgxsnq2kD68NRoR zx9Sz40Qog9OWSoW5f/QZObMrxiIwr9UAxD7/LAcVT+Hs4Qh2g009RuD1ThgI+bGIxBg OX5S80cI41qXRa/cckYiI86Sj79nvn0Il4qMI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=NLAhvcWsUxn1jkbfPek4udMDhz3lWIlFZa4+FJp1SYnXMNzDAP4nmhkTV92ORCiS6W NMn7A+ABM0P8+0NQgIkSt9REja9NB6raqs4ZIquzY2d8+7yfpbiujgblhVvBAh2mmraQ Ma4qMPdmqkZfKy7Bl8a4HCtiNlnN8Zvm9/iBU=
MIME-Version: 1.0
Received: by 10.142.196.1 with SMTP id t1mr1051160wff.71.1260362329326; Wed,  09 Dec 2009 04:38:49 -0800 (PST)
Date: Wed, 9 Dec 2009 20:38:49 +0800
Message-ID: <8b78dd8b0912090438yac15d0fx9520004828ad3a7b@mail.gmail.com>
From: Xiaoyan Jiang <jxyswallow@gmail.com>
To: anthonychan@huawei.com
Content-Type: multipart/alternative; boundary=000e0cd32eb8ed85a8047a4af8e2
Cc: netext@ietf.org
Subject: Re: [netext] draft-chan-netext-distributed-lma-00
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Wed, 09 Dec 2009 12:44:36 -0000

--000e0cd32eb8ed85a8047a4af8e2
Content-Type: text/plain; charset=ISO-8859-1

Hi,Anthony

  Please see in line...

>> Distributed local mobility anchors provides visiting local
>> mobility anchors in different networks with mobility routing >> function
to avoid triangle routing problem in Proxy mobile IP
>> or Mobile IP, but keeps the internetwork location management >> function
at the home local mobility anchors at registered
>> networks.
 -Do the home network and visiting network have to be in the same PMIPv6
domain or not, or is there any restrictions?

>> To perform HoA allocation, each H-LMA may use its own block of >> IP
prefixes to allocate IP addresses to the MNs registering to >> its network.

 - When MN moves from its H-LMA to a V-LMA, how to guarantee the V-LMA has
the authorities to allocate the same HNP to MN?
Do I miss anything?...

Thank you
Xiaoyan Jiang

--000e0cd32eb8ed85a8047a4af8e2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,Anthony<br>=A0<br>=A0 Please see in line... <br>=A0<br>&gt;&gt; Distribu=
ted local mobility anchors provides visiting local <br>&gt;&gt; mobility an=
chors in different networks with mobility routing &gt;&gt; function to avoi=
d triangle routing problem in Proxy mobile IP<br>
&gt;&gt; or Mobile IP, but keeps the internetwork location management &gt;&=
gt; function at the home local mobility anchors at registered <br>&gt;&gt; =
networks.<br>=A0-Do the home network and visiting network have to be in the=
 same PMIPv6 domain or not, or is there any restrictions?<br>
=A0<br>&gt;&gt; To perform HoA allocation, each H-LMA may use its own block=
 of &gt;&gt; IP prefixes to allocate IP addresses to the MNs registering to=
 &gt;&gt; its network.=A0 <br>=A0- When MN moves from its H-LMA to a V-LMA,=
 how to guarantee the V-LMA has the authorities to allocate the same HNP to=
 MN?<br>
Do I miss anything?...<br>=A0<br>Thank you<br>Xiaoyan Jiang

--000e0cd32eb8ed85a8047a4af8e2--

From Basavaraj.Patil@nokia.com  Fri Dec 11 13:57:02 2009
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A319B3A63D3 for <netext@core3.amsl.com>; Fri, 11 Dec 2009 13:57:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_65=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dem+jScS+4Gv for <netext@core3.amsl.com>; Fri, 11 Dec 2009 13:57:01 -0800 (PST)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 8DB143A65A6 for <netext@ietf.org>; Fri, 11 Dec 2009 13:57:00 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id nBBLug1o003334 for <netext@ietf.org>; Fri, 11 Dec 2009 23:56:45 +0200
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 11 Dec 2009 23:56:38 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 11 Dec 2009 23:56:33 +0200
Received: from NOK-EUMSG-03.mgdnok.nokia.com ([65.54.30.108]) by nok-am1mhub-02.mgdnok.nokia.com ([65.54.30.6]) with mapi; Fri, 11 Dec 2009 22:56:33 +0100
From: <Basavaraj.Patil@nokia.com>
To: <netext@ietf.org>
Date: Fri, 11 Dec 2009 22:56:30 +0100
Thread-Topic: IETF76 Meeting minutes
Thread-Index: Acp6rMt2aKtZvWEoSkCdwA0MkjT4Zg==
Message-ID: <C7481C2E.1D74%basavaraj.patil@nokia.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 11 Dec 2009 21:56:33.0995 (UTC) FILETIME=[CDD851B0:01CA7AAC]
X-Nokia-AV: Clean
Subject: [netext] IETF76 Meeting minutes
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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, 11 Dec 2009 21:57:02 -0000

Network-Based Mobility Extensions (netext) WG Minutes
IETF 76

WEDNESDAY, November 11, 2009, 1300-1500 Afternoon Session I

Chairs: Basavaraj Patil (basavaraj.patil@nokia.com)
Rajeev Koodli (rkoodli@starentnetworks.com)

Credit for these minutes to: Antti Makela(antti dot makela at tkk dot fi>

--------------------------------------------------



1. Agenda bashing, Blueseheets, Note takers, Jabber scribes      5 Mins
   Change in agenda: Flow Mobility and Inter-technology handovers moved
   to start due to conflicting schedule.

2. PMIP6 extensions for inter-access, presenters Rajeev Koodli and
   Jari Arkko

http://www.ietf.org/proceedings/09nov/slides/netext-12.ppt
and http://www.ietf.org/proceedings/09nov/slides/netext-6.pdf

Discussion on choices at
http://www.ietf.org/mail-archive/web/netext/current/msg00881.html and
slide 2 of JA's presentation

JA: Recharter or new WG (Netext2?)

Jonne Soininen/NSN: Everything is true, but Solution #1 is not needed
since IP does not notice anything, constrant to 2G/3G handover in 3GPP
JA: With different technologies where MTU changes IP level needs to be
aware
JS: Virtual links depend on operating systems, different on Symbian
and FreeBSD
JA: We shouldn't provide implementation advice, only conceptual
JS: Can it be done in high-level fashion?
Sri: We don't have triggering capability from UE -> MAG. How about
 moving only partial set of flows to a new interface? What is the
 evolution path?=20
JA: Is triggering at L2 or L3? Discussion so far indicated that we
 don't want L3 solution, possible PMIP extensions would transfer
 triggers around the nextwork but they'd still be L2 triggers. With L3
 triggers you  can't have inter-access handovers and PMIP.
Sri: Can build everything on the network site, if triggering is out-of-band=
?
RK:  Regardless of choice with MAG interface signaling needed between
    LMA <-> MAG to allow for subset of flows being transferred

Juan-Carlos Zunlga: MAG <-> MN, Solution recommendations should be
 very specific Carlos J. Bernardos: I support writing BCP document
 Marcello: I think conclusions accurate.

Vote: Reasonable way forward, yes/no: ~ 17 yes, none no.

JA: Expecting text on the discussion as a basis for a minor recharter
Sri: Can triggers come from link-layer and PMIP support it on network side?
JA: Should be ok
Marcelo: There is no standard-track document on this.

3. Runtime LMA Assignment Support for Proxy Mobile IPv6, Jouni
Korhonen http://www.ietf.org/proceedings/09nov/slides/netext-8.ppt
I-D: draft-ietf-netext-redirect-00

About 5 people have read draft
No comments forthcoming

RK: What is the motivation for mid-session LMA assignment?
JK: Currently assignment only applies to initial assignment, input
  needed for motivation - do people find this useful? Applies to
  handover cases where you might cross a boundary where administrator
  has decided to switch LMAs. Lots of assumptions in such cases (sharing
  of mobility sessions etc)
RK: If session is anchored at specific LMA, is there session continuity.
JK: Have you read draft?
RK: No
JK: Open question at the moment, there is introduction to a discussion
  in the draft
RK: I don't think this should be done at all. Why both soft and hard
  support needed? Simpler approach needed, now three-level complexity.
JK: So, take handover exchange away, only apply assignment on initial
PBU/PBA?
RK: Yes

Hidetoshi Yokota: Mid-session redirection, where LMA sends back
 different LMA, session would break.
BP: When you a redirected to new MAG, the session should go to the
 anchored LMA
HY: It's just an example
BP: Bad example.

Kent Leung: Why are we doing LMA reassignment during handover? I don't
 see justification. Question: What is the option in PBU?
JK: If we apply only in initial, we don't use option. Draft doesn't
 comment on options yet.

4. Bulk Re-registration for Proxy Mobile IPv6, Basavaraj Patil
http://www.ietf.org/proceedings/09nov/slides/netext-1.pdf
I-D: draft-premec-netlmm-bulk-re-registration-03

Marcos: Is this same as group ID?
BP: Not to my understanding
Marcos: I propose merging group ID with Charlie's draft
RK: Charlie's draft tries to combine multiple ID's concerining single
 node
Marcos: So, there's a connection, in this case we are just doing it
 for multiple nodes. Better to have all in single draft.
BP: Charlie not here, but we can have different sets of IDs depending
 on policy. We can continue this on list.
Qin Wu: How do you define flag B, it has two purposes, what if both
 purposes happen at same time.
BP: We'll provide a clarification in future revision.

Localized routing - PS and solutions discussion

5. PMIPv6 Localized Routing Problem Statement
http://www.ietf.org/proceedings/09nov/slides/netext-2.ppt
draft-ietf-netext-pmip6-lr-ps-01.txt
BJ: Few people have read the document, please send comments, also on
 the roaming model.
Glen Zoren(?): I was under impression that PMIP domain was set of
 nodes which could set up SA's between each other - so you can have
 dynamic domains.=20
Carlos: That's not incorrect as such, but can't make that assumption.
GZ: I didn't mean all PMIP entities in the world.

6. draft-oulai-netext-opt-local-routing-01.txt,  Suresh Krishnan
http://www.ietf.org/proceedings/09nov/slides/netext-9.ppt
>
Kent Leung: Is the scope limited to some cases only
SK: Yes.
BP: What do you mean by optimized handover?
SK: Not easy problem but if there's RO between MAGs and MN switches
 MAGs, we can use that
KL: Is it possible to map the problem spaces of different solutions to
 different drafts for comparison?
BP: Yes, at least we can talk now about them allow
Marcos: What does it mean "inter-MAG tunnel may be preconfigured"
SK: If some MAGs are close to one another, who can expect handovers
 between them, they can prepare for RO

7. draft-koodli-netext-local-forwarding, Rajeev Koodli
http://www.ietf.org/proceedings/09nov/slides/netext-11.ppt

 ?: What triggers the transaction?
RK: Trigger is still open.
[Several people did not state names]
?2: Two LMA's are not talking to each other, how's the authentication?
RK: If the LMAs trust each other, even if not talking, authentication is ok=
.
 Trust doesn't mean you have to talk. You don't want LMA <-> LMA signaling.
 What's is defined is MAG <-> MAG, with some LMA interaction. What's
 happening is dynamic delegation with fine granularity.
BP: Cutting off discussion

8. draft-wu-netext-local-ro Qin Wu
http://www.ietf.org/proceedings/09nov/slides/netext-3.ppt

Mohana Jeyatharan: LMA needs to know where prefix is from
QW: Ok, we'll address this in next revision

9. draft-loureiro-netext-pmipv6-ro-01.txt
http://www.ietf.org/proceedings/09nov/slides/netext-4.ppt

BP: That concludes discussion on localized routing

10. New Proposals:

Multihoming extensions for Proxy Mobile IPv6 Carlos J. Bernardos I-D:
 draft-bernardos-mif-pmip-01.txt 5 mins

Hui Deng: Clarifications on weak/strong host models?
 BP: Let's take this on mailing list

Service Flow Identifier in Proxy Mobile IPv6
Hui Deng - draft-hui-netext-service-flow-identifier-01.txt   5 Mins

HD: WG draft?
BP: We need to do the rechartering process, then we can consider
 taking this on.

Bulk PBU using Bitmaps
Mohana J. - draft-jeyatharan-netext-pmip-bulkpbu-bitmap-00  5 Mins

MJ: Comments on the way forward?
BP: We have adopted group ID approaches as WG items, for these we need
 to do more discussions on mailing lists.

Virtual interface for supporting multihoming and inter technology
 handover Tranh M. Trung -  draft-trung-netext-virtual-interface-01 5
 Mins

Sri: Can you statement the differences between this and other related
 document(s)?
TMT: I try to limit the modifications to mobile node.
Sri: If it's a simple change, does this require a new document? Better
 work with existing ones
BP: Moving on

ITHO support in MN for PMIP6
Hidetoshi Y./Sri  G. draft-yokota-netlmm-pmipv6-mn-itho-support-02.txt

Reflector Extension for Route Optimization Agent Xiansong Cui
 draft-cui-netext-route-optimization-agent-ext-01.txt 5 Mins

CJB: Why LMA, not MAG doing this? Some work done for RO in Nemo,
 please take a look
BP: Need to shut down and conclude

BP: Meeting adjourned, rest of the presentations not given due to lack
 of time.

Differentiated Services Support for Proxy Mobile IPv6 Behcet S./Frank
 Xia - draft-xia-netext-qos-00.txt

Gateway Initiated Dual-Stack Lite Deployment Sri G.
 draft-gundavelli-softwire-gateway-init-ds-lite-00

PMIPv6 and Network Mobility Problem Statement Carlos CJ.
 draft-bernardos-netext-pmipv6-nemo-ps-00



From Xiangsong.Cui@huawei.com  Sun Dec 13 18:06:58 2009
Return-Path: <Xiangsong.Cui@huawei.com>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6684328C0E0 for <netext@core3.amsl.com>; Sun, 13 Dec 2009 18:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.143
X-Spam-Level: *
X-Spam-Status: No, score=1.143 tagged_above=-999 required=5 tests=[AWL=-1.563,  BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_65=0.6, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-uoYtD9kDjk for <netext@core3.amsl.com>; Sun, 13 Dec 2009 18:06:57 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 914943A67AE for <netext@ietf.org>; Sun, 13 Dec 2009 18:06:52 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KUM00CHWDUJH6@szxga02-in.huawei.com> for netext@ietf.org; Mon, 14 Dec 2009 10:06:20 +0800 (CST)
Received: from c00111037 ([10.111.16.88]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KUM000KQDUJIN@szxga02-in.huawei.com> for netext@ietf.org; Mon, 14 Dec 2009 10:06:19 +0800 (CST)
Date: Mon, 14 Dec 2009 10:06:17 +0800
From: Xiangsong Cui <Xiangsong.Cui@huawei.com>
To: Basavaraj.Patil@nokia.com, netext@ietf.org
Message-id: <00ae01ca7c62$05de89b0$58106f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <C7481C2E.1D74%basavaraj.patil@nokia.com>
Cc: =?iso-8859-1?Q?Antti_M=E4kel=E4?= <antti.makela@tkk.fi>
Subject: [netext] Follow-up on draft-route-optimization-agent // Re: IETF76 Meeting minutes
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Mon, 14 Dec 2009 02:06:58 -0000

Dear Raj and others

> Reflector Extension for Route Optimization Agent Xiansong Cui
> draft-cui-netext-route-optimization-agent-ext-01.txt 5 Mins
> 
> CJB: Why LMA, not MAG doing this? Some work done for RO in Nemo,
> please take a look
> BP: Need to shut down and conclude

For the first comment, I chose MAG to implement the function because the 
agent function looks like a reactive proxy or a keeper gateway for the 
attached MN, so I integrated this function into MAG entity. I do agree that
LMA can do this function, that is OK. I highlight this point in section 3.4 and
4.1 of 02 version.

For the second comment, I had a discussion with Carlos after the F2F 
meeting, and he imparted the related work to me. Thanks Carlos again.
I reflects this comment in section 3.3 of 02 version.

Antti Makela and I have updated the draft to 02 version,
http://tools.ietf.org/id/draft-cui-netext-route-optimization-agent-ext-02.txt
If possible, we wish this draft may be adopted as a WG item.

Any comment is highly appreciated!

Thanks and regards
Xiangsong

----- Original Message ----- 
From: <Basavaraj.Patil@nokia.com>
To: <netext@ietf.org>
Sent: Saturday, December 12, 2009 5:56 AM
Subject: [netext] IETF76 Meeting minutes


> 
> Network-Based Mobility Extensions (netext) WG Minutes
> IETF 76
> 
> WEDNESDAY, November 11, 2009, 1300-1500 Afternoon Session I
> 
> Chairs: Basavaraj Patil (basavaraj.patil@nokia.com)
> Rajeev Koodli (rkoodli@starentnetworks.com)
> 
> Credit for these minutes to: Antti Makela(antti dot makela at tkk dot fi>
> 
> --------------------------------------------------
> 
> 
> 
> 1. Agenda bashing, Blueseheets, Note takers, Jabber scribes      5 Mins
>   Change in agenda: Flow Mobility and Inter-technology handovers moved
>   to start due to conflicting schedule.
> 
> 2. PMIP6 extensions for inter-access, presenters Rajeev Koodli and
>   Jari Arkko
> 
> http://www.ietf.org/proceedings/09nov/slides/netext-12.ppt
> and http://www.ietf.org/proceedings/09nov/slides/netext-6.pdf
> 
> Discussion on choices at
> http://www.ietf.org/mail-archive/web/netext/current/msg00881.html and
> slide 2 of JA's presentation
> 
> JA: Recharter or new WG (Netext2?)
> 
> Jonne Soininen/NSN: Everything is true, but Solution #1 is not needed
> since IP does not notice anything, constrant to 2G/3G handover in 3GPP
> JA: With different technologies where MTU changes IP level needs to be
> aware
> JS: Virtual links depend on operating systems, different on Symbian
> and FreeBSD
> JA: We shouldn't provide implementation advice, only conceptual
> JS: Can it be done in high-level fashion?
> Sri: We don't have triggering capability from UE -> MAG. How about
> moving only partial set of flows to a new interface? What is the
> evolution path? 
> JA: Is triggering at L2 or L3? Discussion so far indicated that we
> don't want L3 solution, possible PMIP extensions would transfer
> triggers around the nextwork but they'd still be L2 triggers. With L3
> triggers you  can't have inter-access handovers and PMIP.
> Sri: Can build everything on the network site, if triggering is out-of-band?
> RK:  Regardless of choice with MAG interface signaling needed between
>    LMA <-> MAG to allow for subset of flows being transferred
> 
> Juan-Carlos Zunlga: MAG <-> MN, Solution recommendations should be
> very specific Carlos J. Bernardos: I support writing BCP document
> Marcello: I think conclusions accurate.
> 
> Vote: Reasonable way forward, yes/no: ~ 17 yes, none no.
> 
> JA: Expecting text on the discussion as a basis for a minor recharter
> Sri: Can triggers come from link-layer and PMIP support it on network side?
> JA: Should be ok
> Marcelo: There is no standard-track document on this.
> 
> 3. Runtime LMA Assignment Support for Proxy Mobile IPv6, Jouni
> Korhonen http://www.ietf.org/proceedings/09nov/slides/netext-8.ppt
> I-D: draft-ietf-netext-redirect-00
> 
> About 5 people have read draft
> No comments forthcoming
> 
> RK: What is the motivation for mid-session LMA assignment?
> JK: Currently assignment only applies to initial assignment, input
>  needed for motivation - do people find this useful? Applies to
>  handover cases where you might cross a boundary where administrator
>  has decided to switch LMAs. Lots of assumptions in such cases (sharing
>  of mobility sessions etc)
> RK: If session is anchored at specific LMA, is there session continuity.
> JK: Have you read draft?
> RK: No
> JK: Open question at the moment, there is introduction to a discussion
>  in the draft
> RK: I don't think this should be done at all. Why both soft and hard
>  support needed? Simpler approach needed, now three-level complexity.
> JK: So, take handover exchange away, only apply assignment on initial
> PBU/PBA?
> RK: Yes
> 
> Hidetoshi Yokota: Mid-session redirection, where LMA sends back
> different LMA, session would break.
> BP: When you a redirected to new MAG, the session should go to the
> anchored LMA
> HY: It's just an example
> BP: Bad example.
> 
> Kent Leung: Why are we doing LMA reassignment during handover? I don't
> see justification. Question: What is the option in PBU?
> JK: If we apply only in initial, we don't use option. Draft doesn't
> comment on options yet.
> 
> 4. Bulk Re-registration for Proxy Mobile IPv6, Basavaraj Patil
> http://www.ietf.org/proceedings/09nov/slides/netext-1.pdf
> I-D: draft-premec-netlmm-bulk-re-registration-03
> 
> Marcos: Is this same as group ID?
> BP: Not to my understanding
> Marcos: I propose merging group ID with Charlie's draft
> RK: Charlie's draft tries to combine multiple ID's concerining single
> node
> Marcos: So, there's a connection, in this case we are just doing it
> for multiple nodes. Better to have all in single draft.
> BP: Charlie not here, but we can have different sets of IDs depending
> on policy. We can continue this on list.
> Qin Wu: How do you define flag B, it has two purposes, what if both
> purposes happen at same time.
> BP: We'll provide a clarification in future revision.
> 
> Localized routing - PS and solutions discussion
> 
> 5. PMIPv6 Localized Routing Problem Statement
> http://www.ietf.org/proceedings/09nov/slides/netext-2.ppt
> draft-ietf-netext-pmip6-lr-ps-01.txt
> BJ: Few people have read the document, please send comments, also on
> the roaming model.
> Glen Zoren(?): I was under impression that PMIP domain was set of
> nodes which could set up SA's between each other - so you can have
> dynamic domains. 
> Carlos: That's not incorrect as such, but can't make that assumption.
> GZ: I didn't mean all PMIP entities in the world.
> 
> 6. draft-oulai-netext-opt-local-routing-01.txt,  Suresh Krishnan
> http://www.ietf.org/proceedings/09nov/slides/netext-9.ppt
>>
> Kent Leung: Is the scope limited to some cases only
> SK: Yes.
> BP: What do you mean by optimized handover?
> SK: Not easy problem but if there's RO between MAGs and MN switches
> MAGs, we can use that
> KL: Is it possible to map the problem spaces of different solutions to
> different drafts for comparison?
> BP: Yes, at least we can talk now about them allow
> Marcos: What does it mean "inter-MAG tunnel may be preconfigured"
> SK: If some MAGs are close to one another, who can expect handovers
> between them, they can prepare for RO
> 
> 7. draft-koodli-netext-local-forwarding, Rajeev Koodli
> http://www.ietf.org/proceedings/09nov/slides/netext-11.ppt
> 
> ?: What triggers the transaction?
> RK: Trigger is still open.
> [Several people did not state names]
> ?2: Two LMA's are not talking to each other, how's the authentication?
> RK: If the LMAs trust each other, even if not talking, authentication is ok.
> Trust doesn't mean you have to talk. You don't want LMA <-> LMA signaling.
> What's is defined is MAG <-> MAG, with some LMA interaction. What's
> happening is dynamic delegation with fine granularity.
> BP: Cutting off discussion
> 
> 8. draft-wu-netext-local-ro Qin Wu
> http://www.ietf.org/proceedings/09nov/slides/netext-3.ppt
> 
> Mohana Jeyatharan: LMA needs to know where prefix is from
> QW: Ok, we'll address this in next revision
> 
> 9. draft-loureiro-netext-pmipv6-ro-01.txt
> http://www.ietf.org/proceedings/09nov/slides/netext-4.ppt
> 
> BP: That concludes discussion on localized routing
> 
> 10. New Proposals:
> 
> Multihoming extensions for Proxy Mobile IPv6 Carlos J. Bernardos I-D:
> draft-bernardos-mif-pmip-01.txt 5 mins
> 
> Hui Deng: Clarifications on weak/strong host models?
> BP: Let's take this on mailing list
> 
> Service Flow Identifier in Proxy Mobile IPv6
> Hui Deng - draft-hui-netext-service-flow-identifier-01.txt   5 Mins
> 
> HD: WG draft?
> BP: We need to do the rechartering process, then we can consider
> taking this on.
> 
> Bulk PBU using Bitmaps
> Mohana J. - draft-jeyatharan-netext-pmip-bulkpbu-bitmap-00  5 Mins
> 
> MJ: Comments on the way forward?
> BP: We have adopted group ID approaches as WG items, for these we need
> to do more discussions on mailing lists.
> 
> Virtual interface for supporting multihoming and inter technology
> handover Tranh M. Trung -  draft-trung-netext-virtual-interface-01 5
> Mins
> 
> Sri: Can you statement the differences between this and other related
> document(s)?
> TMT: I try to limit the modifications to mobile node.
> Sri: If it's a simple change, does this require a new document? Better
> work with existing ones
> BP: Moving on
> 
> ITHO support in MN for PMIP6
> Hidetoshi Y./Sri  G. draft-yokota-netlmm-pmipv6-mn-itho-support-02.txt
> 
> Reflector Extension for Route Optimization Agent Xiansong Cui
> draft-cui-netext-route-optimization-agent-ext-01.txt 5 Mins
> 
> CJB: Why LMA, not MAG doing this? Some work done for RO in Nemo,
> please take a look
> BP: Need to shut down and conclude
> 
> BP: Meeting adjourned, rest of the presentations not given due to lack
> of time.
> 
> Differentiated Services Support for Proxy Mobile IPv6 Behcet S./Frank
> Xia - draft-xia-netext-qos-00.txt
> 
> Gateway Initiated Dual-Stack Lite Deployment Sri G.
> draft-gundavelli-softwire-gateway-init-ds-lite-00
> 
> PMIPv6 and Network Mobility Problem Statement Carlos CJ.
> draft-bernardos-netext-pmipv6-nemo-ps-00
> 
> 
> _______________________________________________
> netext mailing list
> netext@ietf.org
> https://www.ietf.org/mailman/listinfo/netext

From jxyswallow@gmail.com  Mon Dec 14 01:22:47 2009
Return-Path: <jxyswallow@gmail.com>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E92C3A69D0 for <netext@core3.amsl.com>; Mon, 14 Dec 2009 01:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.211
X-Spam-Level: 
X-Spam-Status: No, score=0.211 tagged_above=-999 required=5 tests=[AWL=-2.069,  BAYES_05=-1.11, CN_BODY_35=0.339, HTML_MESSAGE=0.001, J_CHICKENPOX_65=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXIh-aMMaR2X for <netext@core3.amsl.com>; Mon, 14 Dec 2009 01:22:25 -0800 (PST)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id 8913E3A69CB for <netext@ietf.org>; Mon, 14 Dec 2009 01:22:25 -0800 (PST)
Received: by pwi20 with SMTP id 20so1992012pwi.29 for <netext@ietf.org>; Mon, 14 Dec 2009 01:22:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=tkkqhxf7E4SO9o+vMlUvkpIrmhuc7Mt0ydXu+oTYZ7U=; b=x4WS8VJZBa5UW6DM2p5tR/M1wUbuSnx0EmExUnZ4UHjmxq1Mybn5As6/xHB6zW6O53 i0Q1jQzLbfnDEH+e4SLBWzROcqryuKy5iMzrQ+6D53NI1YuM1H0KgWbVFyPyXYqErnrQ sG/ZdkU2LZIjC2lvRx6erXh/xTwnVzFjgWHMQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=A/lQ7ViOEIDFM9mTg4Ls9Trnnl8cNALwYKdcNRnnN7ZD2dEbVaYA2pgdb2TjnazHMj Ixx2DwJtoqQg8VmnAbp9w8MqJKluP02Mo7VJUioST/1m5wlAy6Wp+waob37tsxyLw1Kj mhha3cpDBCvOnY9+nD87zaWcnE6Gx4u0Xytq4=
MIME-Version: 1.0
Received: by 10.143.138.7 with SMTP id q7mr2932405wfn.314.1260782530050; Mon,  14 Dec 2009 01:22:10 -0800 (PST)
In-Reply-To: <mailman.8.1260648002.310.netext@ietf.org>
References: <mailman.8.1260648002.310.netext@ietf.org>
Date: Mon, 14 Dec 2009 17:22:10 +0800
Message-ID: <8b78dd8b0912140122m5b6f7dbfue939c593ca5ec194@mail.gmail.com>
From: Xiaoyan Jiang <jxyswallow@gmail.com>
To: netext@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd5f6fad7c3c1047aacceca
Subject: Re: [netext] netext Digest, Vol 7, Issue 2
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Mon, 14 Dec 2009 09:22:47 -0000

--000e0cd5f6fad7c3c1047aacceca
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

About PMIP6 extensions for inter-access, I don't understand soution 2 well.
How does MN provide the handover information to MAG or other entity? What's
the relationship between soution 2 and soution 3?

2009/12/13 <netext-request@ietf.org>

> If you have received this digest without all the individual message
> attachments you will need to update your digest options in your list
> subscription.  To do so, go to
>
> https://www.ietf.org/mailman/listinfo/netext
>
> Click the 'Unsubscribe or edit options' button, log in, and set "Get
> MIME or Plain Text Digests?" to MIME.  You can set this option
> globally for all the list digests you receive at this point.
>
>
>
> Send netext mailing list submissions to
>        netext@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://www.ietf.org/mailman/listinfo/netext
> or, via email, send a message with subject or body 'help' to
>        netext-request@ietf.org
>
> You can reach the person managing the list at
>        netext-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of netext digest..."
>
> Today's Topics:
>
>   1. IETF76 Meeting minutes (Basavaraj.Patil@nokia.com)
>
>
> ---------- =D2=D1=D7=AA=B7=A2=D3=CA=BC=FE ----------
> From: <Basavaraj.Patil@nokia.com>
> To: <netext@ietf.org>
> Date: Fri, 11 Dec 2009 22:56:30 +0100
> Subject: [netext] IETF76 Meeting minutes
>
> Network-Based Mobility Extensions (netext) WG Minutes
> IETF 76
>
> WEDNESDAY, November 11, 2009, 1300-1500 Afternoon Session I
>
> Chairs: Basavaraj Patil (basavaraj.patil@nokia.com)
> Rajeev Koodli (rkoodli@starentnetworks.com)
>
> Credit for these minutes to: Antti Makela(antti dot makela at tkk dot fi>
>
> --------------------------------------------------
>
>
>
> 1. Agenda bashing, Blueseheets, Note takers, Jabber scribes      5 Mins
>   Change in agenda: Flow Mobility and Inter-technology handovers moved
>   to start due to conflicting schedule.
>
> 2. PMIP6 extensions for inter-access, presenters Rajeev Koodli and
>   Jari Arkko
>
> http://www.ietf.org/proceedings/09nov/slides/netext-12.ppt
> and http://www.ietf.org/proceedings/09nov/slides/netext-6.pdf
>
> Discussion on choices at
> http://www.ietf.org/mail-archive/web/netext/current/msg00881.html and
> slide 2 of JA's presentation
>
> JA: Recharter or new WG (Netext2?)
>
> Jonne Soininen/NSN: Everything is true, but Solution #1 is not needed
> since IP does not notice anything, constrant to 2G/3G handover in 3GPP
> JA: With different technologies where MTU changes IP level needs to be
> aware
> JS: Virtual links depend on operating systems, different on Symbian
> and FreeBSD
> JA: We shouldn't provide implementation advice, only conceptual
> JS: Can it be done in high-level fashion?
> Sri: We don't have triggering capability from UE -> MAG. How about
>  moving only partial set of flows to a new interface? What is the
>  evolution path?
> JA: Is triggering at L2 or L3? Discussion so far indicated that we
>  don't want L3 solution, possible PMIP extensions would transfer
>  triggers around the nextwork but they'd still be L2 triggers. With L3
>  triggers you  can't have inter-access handovers and PMIP.
> Sri: Can build everything on the network site, if triggering is
> out-of-band?
> RK:  Regardless of choice with MAG interface signaling needed between
>    LMA <-> MAG to allow for subset of flows being transferred
>
> Juan-Carlos Zunlga: MAG <-> MN, Solution recommendations should be
>  very specific Carlos J. Bernardos: I support writing BCP document
>  Marcello: I think conclusions accurate.
>
> Vote: Reasonable way forward, yes/no: ~ 17 yes, none no.
>
> JA: Expecting text on the discussion as a basis for a minor recharter
> Sri: Can triggers come from link-layer and PMIP support it on network sid=
e?
> JA: Should be ok
> Marcelo: There is no standard-track document on this.
>
> 3. Runtime LMA Assignment Support for Proxy Mobile IPv6, Jouni
> Korhonen http://www.ietf.org/proceedings/09nov/slides/netext-8.ppt
> I-D: draft-ietf-netext-redirect-00
>
> About 5 people have read draft
> No comments forthcoming
>
> RK: What is the motivation for mid-session LMA assignment?
> JK: Currently assignment only applies to initial assignment, input
>  needed for motivation - do people find this useful? Applies to
>  handover cases where you might cross a boundary where administrator
>  has decided to switch LMAs. Lots of assumptions in such cases (sharing
>  of mobility sessions etc)
> RK: If session is anchored at specific LMA, is there session continuity.
> JK: Have you read draft?
> RK: No
> JK: Open question at the moment, there is introduction to a discussion
>  in the draft
> RK: I don't think this should be done at all. Why both soft and hard
>  support needed? Simpler approach needed, now three-level complexity.
> JK: So, take handover exchange away, only apply assignment on initial
> PBU/PBA?
> RK: Yes
>
> Hidetoshi Yokota: Mid-session redirection, where LMA sends back
>  different LMA, session would break.
> BP: When you a redirected to new MAG, the session should go to the
>  anchored LMA
> HY: It's just an example
> BP: Bad example.
>
> Kent Leung: Why are we doing LMA reassignment during handover? I don't
>  see justification. Question: What is the option in PBU?
> JK: If we apply only in initial, we don't use option. Draft doesn't
>  comment on options yet.
>
> 4. Bulk Re-registration for Proxy Mobile IPv6, Basavaraj Patil
> http://www.ietf.org/proceedings/09nov/slides/netext-1.pdf
> I-D: draft-premec-netlmm-bulk-re-registration-03
>
> Marcos: Is this same as group ID?
> BP: Not to my understanding
> Marcos: I propose merging group ID with Charlie's draft
> RK: Charlie's draft tries to combine multiple ID's concerining single
>  node
> Marcos: So, there's a connection, in this case we are just doing it
>  for multiple nodes. Better to have all in single draft.
> BP: Charlie not here, but we can have different sets of IDs depending
>  on policy. We can continue this on list.
> Qin Wu: How do you define flag B, it has two purposes, what if both
>  purposes happen at same time.
> BP: We'll provide a clarification in future revision.
>
> Localized routing - PS and solutions discussion
>
> 5. PMIPv6 Localized Routing Problem Statement
> http://www.ietf.org/proceedings/09nov/slides/netext-2.ppt
> draft-ietf-netext-pmip6-lr-ps-01.txt
> BJ: Few people have read the document, please send comments, also on
>  the roaming model.
> Glen Zoren(?): I was under impression that PMIP domain was set of
>  nodes which could set up SA's between each other - so you can have
>  dynamic domains.
> Carlos: That's not incorrect as such, but can't make that assumption.
> GZ: I didn't mean all PMIP entities in the world.
>
> 6. draft-oulai-netext-opt-local-routing-01.txt,  Suresh Krishnan
> http://www.ietf.org/proceedings/09nov/slides/netext-9.ppt
> >
> Kent Leung: Is the scope limited to some cases only
> SK: Yes.
> BP: What do you mean by optimized handover?
> SK: Not easy problem but if there's RO between MAGs and MN switches
>  MAGs, we can use that
> KL: Is it possible to map the problem spaces of different solutions to
>  different drafts for comparison?
> BP: Yes, at least we can talk now about them allow
> Marcos: What does it mean "inter-MAG tunnel may be preconfigured"
> SK: If some MAGs are close to one another, who can expect handovers
>  between them, they can prepare for RO
>
> 7. draft-koodli-netext-local-forwarding, Rajeev Koodli
> http://www.ietf.org/proceedings/09nov/slides/netext-11.ppt
>
>  ?: What triggers the transaction?
> RK: Trigger is still open.
> [Several people did not state names]
> ?2: Two LMA's are not talking to each other, how's the authentication?
> RK: If the LMAs trust each other, even if not talking, authentication is
> ok.
>  Trust doesn't mean you have to talk. You don't want LMA <-> LMA signalin=
g.
>  What's is defined is MAG <-> MAG, with some LMA interaction. What's
>  happening is dynamic delegation with fine granularity.
> BP: Cutting off discussion
>
> 8. draft-wu-netext-local-ro Qin Wu
> http://www.ietf.org/proceedings/09nov/slides/netext-3.ppt
>
> Mohana Jeyatharan: LMA needs to know where prefix is from
> QW: Ok, we'll address this in next revision
>
> 9. draft-loureiro-netext-pmipv6-ro-01.txt
> http://www.ietf.org/proceedings/09nov/slides/netext-4.ppt
>
> BP: That concludes discussion on localized routing
>
> 10. New Proposals:
>
> Multihoming extensions for Proxy Mobile IPv6 Carlos J. Bernardos I-D:
>  draft-bernardos-mif-pmip-01.txt 5 mins
>
> Hui Deng: Clarifications on weak/strong host models?
>  BP: Let's take this on mailing list
>
> Service Flow Identifier in Proxy Mobile IPv6
> Hui Deng - draft-hui-netext-service-flow-identifier-01.txt   5 Mins
>
> HD: WG draft?
> BP: We need to do the rechartering process, then we can consider
>  taking this on.
>
> Bulk PBU using Bitmaps
> Mohana J. - draft-jeyatharan-netext-pmip-bulkpbu-bitmap-00  5 Mins
>
> MJ: Comments on the way forward?
> BP: We have adopted group ID approaches as WG items, for these we need
>  to do more discussions on mailing lists.
>
> Virtual interface for supporting multihoming and inter technology
>  handover Tranh M. Trung -  draft-trung-netext-virtual-interface-01 5
>  Mins
>
> Sri: Can you statement the differences between this and other related
>  document(s)?
> TMT: I try to limit the modifications to mobile node.
> Sri: If it's a simple change, does this require a new document? Better
>  work with existing ones
> BP: Moving on
>
> ITHO support in MN for PMIP6
> Hidetoshi Y./Sri  G. draft-yokota-netlmm-pmipv6-mn-itho-support-02.txt
>
> Reflector Extension for Route Optimization Agent Xiansong Cui
>  draft-cui-netext-route-optimization-agent-ext-01.txt 5 Mins
>
> CJB: Why LMA, not MAG doing this? Some work done for RO in Nemo,
>  please take a look
> BP: Need to shut down and conclude
>
> BP: Meeting adjourned, rest of the presentations not given due to lack
>  of time.
>
> Differentiated Services Support for Proxy Mobile IPv6 Behcet S./Frank
>  Xia - draft-xia-netext-qos-00.txt
>
> Gateway Initiated Dual-Stack Lite Deployment Sri G.
>  draft-gundavelli-softwire-gateway-init-ds-lite-00
>
> PMIPv6 and Network Mobility Problem Statement Carlos CJ.
>  draft-bernardos-netext-pmipv6-nemo-ps-00
>
>
>
>
> _______________________________________________
> netext mailing list
> netext@ietf.org
> https://www.ietf.org/mailman/listinfo/netext
>
>

--000e0cd5f6fad7c3c1047aacceca
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

About&nbsp;PMIP6 extensions for inter-access, I don&#39;t understand soutio=
n 2 well. How does&nbsp;MN provide the handover information to MAG or other=
 entity? What&#39;s the relationship between soution 2 and soution 3?<br><b=
r>
<div class=3D"gmail_quote">2009/12/13 <span dir=3D"ltr">&lt;<a href=3D"mail=
to:netext-request@ietf.org">netext-request@ietf.org</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">If you have received this digest=
 without all the individual message<br>attachments you will need to update =
your digest options in your list<br>
subscription. &nbsp;To do so, go to<br><br><a href=3D"https://www.ietf.org/=
mailman/listinfo/netext" target=3D"_blank">https://www.ietf.org/mailman/lis=
tinfo/netext</a><br><br>Click the &#39;Unsubscribe or edit options&#39; but=
ton, log in, and set &quot;Get<br>
MIME or Plain Text Digests?&quot; to MIME. &nbsp;You can set this option<br=
>globally for all the list digests you receive at this point.<br><br><br><b=
r>Send netext mailing list submissions to<br>&nbsp; &nbsp; &nbsp; &nbsp;<a =
href=3D"mailto:netext@ietf.org">netext@ietf.org</a><br>
<br>To subscribe or unsubscribe via the World Wide Web, visit<br>&nbsp; &nb=
sp; &nbsp; &nbsp;<a href=3D"https://www.ietf.org/mailman/listinfo/netext" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/netext</a><br>or, vi=
a email, send a message with subject or body &#39;help&#39; to<br>
&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:netext-request@ietf.org">netex=
t-request@ietf.org</a><br><br>You can reach the person managing the list at=
<br>&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:netext-owner@ietf.org">net=
ext-owner@ietf.org</a><br><br>When replying, please edit your Subject line =
so it is more specific<br>
than &quot;Re: Contents of netext digest...&quot;<br><br>Today&#39;s Topics=
:<br><br>&nbsp; 1. IETF76 Meeting minutes (<a href=3D"mailto:Basavaraj.Pati=
l@nokia.com">Basavaraj.Patil@nokia.com</a>)<br><br><br>---------- =D2=D1=D7=
=AA=B7=A2=D3=CA=BC=FE ----------<br>
From:&nbsp;&lt;<a href=3D"mailto:Basavaraj.Patil@nokia.com">Basavaraj.Patil=
@nokia.com</a>&gt;<br>To:&nbsp;&lt;<a href=3D"mailto:netext@ietf.org">netex=
t@ietf.org</a>&gt;<br>Date:&nbsp;Fri, 11 Dec 2009 22:56:30 +0100<br>Subject=
:&nbsp;[netext] IETF76 Meeting minutes<br>
<br>Network-Based Mobility Extensions (netext) WG Minutes<br>IETF 76<br><br=
>WEDNESDAY, November 11, 2009, 1300-1500 Afternoon Session I<br><br>Chairs:=
 Basavaraj Patil (<a href=3D"mailto:basavaraj.patil@nokia.com">basavaraj.pa=
til@nokia.com</a>)<br>
Rajeev Koodli (<a href=3D"mailto:rkoodli@starentnetworks.com">rkoodli@stare=
ntnetworks.com</a>)<br><br>Credit for these minutes to: Antti Makela(antti =
dot makela at tkk dot fi&gt;<br><br>---------------------------------------=
-----------<br>
<br><br><br>1. Agenda bashing, Blueseheets, Note takers, Jabber scribes &nb=
sp; &nbsp; &nbsp;5 Mins<br>&nbsp; Change in agenda: Flow Mobility and Inter=
-technology handovers moved<br>&nbsp; to start due to conflicting schedule.=
<br><br>2. PMIP6 extensions for inter-access, presenters Rajeev Koodli and<=
br>
&nbsp; Jari Arkko<br><br><a href=3D"http://www.ietf.org/proceedings/09nov/s=
lides/netext-12.ppt" target=3D"_blank">http://www.ietf.org/proceedings/09no=
v/slides/netext-12.ppt</a><br>and <a href=3D"http://www.ietf.org/proceeding=
s/09nov/slides/netext-6.pdf" target=3D"_blank">http://www.ietf.org/proceedi=
ngs/09nov/slides/netext-6.pdf</a><br>
<br>Discussion on choices at<br><a href=3D"http://www.ietf.org/mail-archive=
/web/netext/current/msg00881.html" target=3D"_blank">http://www.ietf.org/ma=
il-archive/web/netext/current/msg00881.html</a> and<br>slide 2 of JA&#39;s =
presentation<br>
<br>JA: Recharter or new WG (Netext2?)<br><br>Jonne Soininen/NSN: Everythin=
g is true, but Solution #1 is not needed<br>since IP does not notice anythi=
ng, constrant to 2G/3G handover in 3GPP<br>JA: With different technologies =
where MTU changes IP level needs to be<br>
aware<br>JS: Virtual links depend on operating systems, different on Symbia=
n<br>and FreeBSD<br>JA: We shouldn&#39;t provide implementation advice, onl=
y conceptual<br>JS: Can it be done in high-level fashion?<br>Sri: We don&#3=
9;t have triggering capability from UE -&gt; MAG. How about<br>
&nbsp;moving only partial set of flows to a new interface? What is the<br>&=
nbsp;evolution path?<br>JA: Is triggering at L2 or L3? Discussion so far in=
dicated that we<br>&nbsp;don&#39;t want L3 solution, possible PMIP extensio=
ns would transfer<br>
&nbsp;triggers around the nextwork but they&#39;d still be L2 triggers. Wit=
h L3<br>&nbsp;triggers you &nbsp;can&#39;t have inter-access handovers and =
PMIP.<br>Sri: Can build everything on the network site, if triggering is ou=
t-of-band?<br>
RK: &nbsp;Regardless of choice with MAG interface signaling needed between<=
br>&nbsp; &nbsp;LMA &lt;-&gt; MAG to allow for subset of flows being transf=
erred<br><br>Juan-Carlos Zunlga: MAG &lt;-&gt; MN, Solution recommendations=
 should be<br>
&nbsp;very specific Carlos J. Bernardos: I support writing BCP document<br>=
&nbsp;Marcello: I think conclusions accurate.<br><br>Vote: Reasonable way f=
orward, yes/no: ~ 17 yes, none no.<br><br>JA: Expecting text on the discuss=
ion as a basis for a minor recharter<br>
Sri: Can triggers come from link-layer and PMIP support it on network side?=
<br>JA: Should be ok<br>Marcelo: There is no standard-track document on thi=
s.<br><br>3. Runtime LMA Assignment Support for Proxy Mobile IPv6, Jouni<br=
>
Korhonen <a href=3D"http://www.ietf.org/proceedings/09nov/slides/netext-8.p=
pt" target=3D"_blank">http://www.ietf.org/proceedings/09nov/slides/netext-8=
.ppt</a><br>I-D: draft-ietf-netext-redirect-00<br><br>About 5 people have r=
ead draft<br>
No comments forthcoming<br><br>RK: What is the motivation for mid-session L=
MA assignment?<br>JK: Currently assignment only applies to initial assignme=
nt, input<br>&nbsp;needed for motivation - do people find this useful? Appl=
ies to<br>
&nbsp;handover cases where you might cross a boundary where administrator<b=
r>&nbsp;has decided to switch LMAs. Lots of assumptions in such cases (shar=
ing<br>&nbsp;of mobility sessions etc)<br>RK: If session is anchored at spe=
cific LMA, is there session continuity.<br>
JK: Have you read draft?<br>RK: No<br>JK: Open question at the moment, ther=
e is introduction to a discussion<br>&nbsp;in the draft<br>RK: I don&#39;t =
think this should be done at all. Why both soft and hard<br>&nbsp;support n=
eeded? Simpler approach needed, now three-level complexity.<br>
JK: So, take handover exchange away, only apply assignment on initial<br>PB=
U/PBA?<br>RK: Yes<br><br>Hidetoshi Yokota: Mid-session redirection, where L=
MA sends back<br>&nbsp;different LMA, session would break.<br>BP: When you =
a redirected to new MAG, the session should go to the<br>
&nbsp;anchored LMA<br>HY: It&#39;s just an example<br>BP: Bad example.<br><=
br>Kent Leung: Why are we doing LMA reassignment during handover? I don&#39=
;t<br>&nbsp;see justification. Question: What is the option in PBU?<br>JK: =
If we apply only in initial, we don&#39;t use option. Draft doesn&#39;t<br>
&nbsp;comment on options yet.<br><br>4. Bulk Re-registration for Proxy Mobi=
le IPv6, Basavaraj Patil<br><a href=3D"http://www.ietf.org/proceedings/09no=
v/slides/netext-1.pdf" target=3D"_blank">http://www.ietf.org/proceedings/09=
nov/slides/netext-1.pdf</a><br>
I-D: draft-premec-netlmm-bulk-re-registration-03<br><br>Marcos: Is this sam=
e as group ID?<br>BP: Not to my understanding<br>Marcos: I propose merging =
group ID with Charlie&#39;s draft<br>RK: Charlie&#39;s draft tries to combi=
ne multiple ID&#39;s concerining single<br>
&nbsp;node<br>Marcos: So, there&#39;s a connection, in this case we are jus=
t doing it<br>&nbsp;for multiple nodes. Better to have all in single draft.=
<br>BP: Charlie not here, but we can have different sets of IDs depending<b=
r>&nbsp;on policy. We can continue this on list.<br>
Qin Wu: How do you define flag B, it has two purposes, what if both<br>&nbs=
p;purposes happen at same time.<br>BP: We&#39;ll provide a clarification in=
 future revision.<br><br>Localized routing - PS and solutions discussion<br=
>
<br>5. PMIPv6 Localized Routing Problem Statement<br><a href=3D"http://www.=
ietf.org/proceedings/09nov/slides/netext-2.ppt" target=3D"_blank">http://ww=
w.ietf.org/proceedings/09nov/slides/netext-2.ppt</a><br>draft-ietf-netext-p=
mip6-lr-ps-01.txt<br>
BJ: Few people have read the document, please send comments, also on<br>&nb=
sp;the roaming model.<br>Glen Zoren(?): I was under impression that PMIP do=
main was set of<br>&nbsp;nodes which could set up SA&#39;s between each oth=
er - so you can have<br>
&nbsp;dynamic domains.<br>Carlos: That&#39;s not incorrect as such, but can=
&#39;t make that assumption.<br>GZ: I didn&#39;t mean all PMIP entities in =
the world.<br><br>6. draft-oulai-netext-opt-local-routing-01.txt, &nbsp;Sur=
esh Krishnan<br>
<a href=3D"http://www.ietf.org/proceedings/09nov/slides/netext-9.ppt" targe=
t=3D"_blank">http://www.ietf.org/proceedings/09nov/slides/netext-9.ppt</a><=
br>&gt;<br>Kent Leung: Is the scope limited to some cases only<br>SK: Yes.<=
br>
BP: What do you mean by optimized handover?<br>SK: Not easy problem but if =
there&#39;s RO between MAGs and MN switches<br>&nbsp;MAGs, we can use that<=
br>KL: Is it possible to map the problem spaces of different solutions to<b=
r>
&nbsp;different drafts for comparison?<br>BP: Yes, at least we can talk now=
 about them allow<br>Marcos: What does it mean &quot;inter-MAG tunnel may b=
e preconfigured&quot;<br>SK: If some MAGs are close to one another, who can=
 expect handovers<br>
&nbsp;between them, they can prepare for RO<br><br>7. draft-koodli-netext-l=
ocal-forwarding, Rajeev Koodli<br><a href=3D"http://www.ietf.org/proceeding=
s/09nov/slides/netext-11.ppt" target=3D"_blank">http://www.ietf.org/proceed=
ings/09nov/slides/netext-11.ppt</a><br>
<br>&nbsp;?: What triggers the transaction?<br>RK: Trigger is still open.<b=
r>[Several people did not state names]<br>?2: Two LMA&#39;s are not talking=
 to each other, how&#39;s the authentication?<br>RK: If the LMAs trust each=
 other, even if not talking, authentication is ok.<br>
&nbsp;Trust doesn&#39;t mean you have to talk. You don&#39;t want LMA &lt;-=
&gt; LMA signaling.<br>&nbsp;What&#39;s is defined is MAG &lt;-&gt; MAG, wi=
th some LMA interaction. What&#39;s<br>&nbsp;happening is dynamic delegatio=
n with fine granularity.<br>
BP: Cutting off discussion<br><br>8. draft-wu-netext-local-ro Qin Wu<br><a =
href=3D"http://www.ietf.org/proceedings/09nov/slides/netext-3.ppt" target=
=3D"_blank">http://www.ietf.org/proceedings/09nov/slides/netext-3.ppt</a><b=
r>
<br>Mohana Jeyatharan: LMA needs to know where prefix is from<br>QW: Ok, we=
&#39;ll address this in next revision<br><br>9. draft-loureiro-netext-pmipv=
6-ro-01.txt<br><a href=3D"http://www.ietf.org/proceedings/09nov/slides/nete=
xt-4.ppt" target=3D"_blank">http://www.ietf.org/proceedings/09nov/slides/ne=
text-4.ppt</a><br>
<br>BP: That concludes discussion on localized routing<br><br>10. New Propo=
sals:<br><br>Multihoming extensions for Proxy Mobile IPv6 Carlos J. Bernard=
os I-D:<br>&nbsp;draft-bernardos-mif-pmip-01.txt 5 mins<br><br>Hui Deng: Cl=
arifications on weak/strong host models?<br>
&nbsp;BP: Let&#39;s take this on mailing list<br><br>Service Flow Identifie=
r in Proxy Mobile IPv6<br>Hui Deng - draft-hui-netext-service-flow-identifi=
er-01.txt &nbsp; 5 Mins<br><br>HD: WG draft?<br>BP: We need to do the recha=
rtering process, then we can consider<br>
&nbsp;taking this on.<br><br>Bulk PBU using Bitmaps<br>Mohana J. - draft-je=
yatharan-netext-pmip-bulkpbu-bitmap-00 &nbsp;5 Mins<br><br>MJ: Comments on =
the way forward?<br>BP: We have adopted group ID approaches as WG items, fo=
r these we need<br>
&nbsp;to do more discussions on mailing lists.<br><br>Virtual interface for=
 supporting multihoming and inter technology<br>&nbsp;handover Tranh M. Tru=
ng - &nbsp;draft-trung-netext-virtual-interface-01 5<br>&nbsp;Mins<br><br>S=
ri: Can you statement the differences between this and other related<br>
&nbsp;document(s)?<br>TMT: I try to limit the modifications to mobile node.=
<br>Sri: If it&#39;s a simple change, does this require a new document? Bet=
ter<br>&nbsp;work with existing ones<br>BP: Moving on<br><br>ITHO support i=
n MN for PMIP6<br>
Hidetoshi Y./Sri &nbsp;G. draft-yokota-netlmm-pmipv6-mn-itho-support-02.txt=
<br><br>Reflector Extension for Route Optimization Agent Xiansong Cui<br>&n=
bsp;draft-cui-netext-route-optimization-agent-ext-01.txt 5 Mins<br><br>CJB:=
 Why LMA, not MAG doing this? Some work done for RO in Nemo,<br>
&nbsp;please take a look<br>BP: Need to shut down and conclude<br><br>BP: M=
eeting adjourned, rest of the presentations not given due to lack<br>&nbsp;=
of time.<br><br>Differentiated Services Support for Proxy Mobile IPv6 Behce=
t S./Frank<br>
&nbsp;Xia - draft-xia-netext-qos-00.txt<br><br>Gateway Initiated Dual-Stack=
 Lite Deployment Sri G.<br>&nbsp;draft-gundavelli-softwire-gateway-init-ds-=
lite-00<br><br>PMIPv6 and Network Mobility Problem Statement Carlos CJ.<br>=
&nbsp;draft-bernardos-netext-pmipv6-nemo-ps-00<br>
<br><br><br><br>_______________________________________________<br>netext m=
ailing list<br><a href=3D"mailto:netext@ietf.org">netext@ietf.org</a><br><a=
 href=3D"https://www.ietf.org/mailman/listinfo/netext" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/netext</a><br>
<br></blockquote></div><br>

--000e0cd5f6fad7c3c1047aacceca--
