Re: [netlmm] About the Agenda for the meeting - your input is needed

Behcet Sarikaya <behcetsarikaya@yahoo.com> Mon, 03 March 2008 15:51 UTC

Return-Path: <netlmm-bounces@ietf.org>
X-Original-To: ietfarch-netlmm-archive@core3.amsl.com
Delivered-To: ietfarch-netlmm-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7E8D28C10F; Mon, 3 Mar 2008 07:51:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.444
X-Spam-Level:
X-Spam-Status: No, score=0.444 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
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 dfPX3nMnOXHf; Mon, 3 Mar 2008 07:50:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10BDC28C0FD; Mon, 3 Mar 2008 07:50:57 -0800 (PST)
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5256C3A6993 for <netlmm@core3.amsl.com>; Mon, 3 Mar 2008 07:50:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 BOFerBBcuUxg for <netlmm@core3.amsl.com>; Mon, 3 Mar 2008 07:50:50 -0800 (PST)
Received: from web84112.mail.mud.yahoo.com (web84112.mail.mud.yahoo.com [68.142.206.199]) by core3.amsl.com (Postfix) with SMTP id 35B083A6864 for <netlmm@ietf.org>; Mon, 3 Mar 2008 07:50:50 -0800 (PST)
Received: (qmail 42229 invoked by uid 60001); 3 Mar 2008 15:50:41 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=skDSQqmV6g8M9xbvQN/BKjl29fPrUH1GOBvQkwmQO1iYchX26cd4du4rvTrA72myJQlidto1UsRJwer38FSPG8I5vbCt4J/VxjMSCdkqhZjznogvEfOa7/I4rDu7bWcdd9RT2dC/CS/Etsue7U5Y8QlUfG0Sp0mikkPNTKgmRLM=;
X-YMail-OSG: UrJPvHYVM1nUZ9vKJYQeBXMSzEd_ZEtGZtMTscaYJHh1XJUCIUhvRtveyeguVlS3_8g5442Sonn3MYy9aiCbc_S433o44frG4f6OBH_6fKiR_aI-
Received: from [206.16.17.212] by web84112.mail.mud.yahoo.com via HTTP; Mon, 03 Mar 2008 07:50:40 PST
X-Mailer: YahooMailRC/818.31 YahooMailWebService/0.7.162
Date: Mon, 03 Mar 2008 07:50:40 -0800
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: "Soininen Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>, ext Frank Xia <xiayangsong@huawei.com>
MIME-Version: 1.0
Message-ID: <833424.40765.qm@web84112.mail.mud.yahoo.com>
Cc: netlmm@ietf.org
Subject: Re: [netlmm] About the Agenda for the meeting - your input is needed
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0118630792=="
Sender: netlmm-bounces@ietf.org
Errors-To: netlmm-bounces@ietf.org

Hi Jonne,
  MIP6 bootstrapping work which involved Radius extensions has been done in MIP6 WG not in radext. 
  The examples are:
RADIUS Mobile IPv6 Support http://tools.ietf.org/id/draft-ietf-mip6-radius-03.txt
if you read RFC 5026 on MIP6 Bootstrapping in Split Scenario, it says that Radius extensions are defined in mip6-radius draft.
  To my knowledge, radext WG was never involved in MIP6 bootstrapping  work, do you think that they would be willing to involve in PMIP6 bootstrapping work?
  Regards,

Behcet
----- Original Message ----
From: Soininen Jonne (NSN - FI/Espoo) <jonne.soininen@nsn.com>
To: ext Frank Xia <xiayangsong@huawei.com>
Cc: netlmm@ietf.org
Sent: Monday, March 3, 2008 9:14:20 AM
Subject: Re: [netlmm] About the Agenda for the meeting - your input is needed


Frank,

I 
thought 
radius 
extensions 
would 
rather 
be 
at 
radext 
WG 
than 
in 
netlmm. 
This 
would 
then 
be 
in 
line 
with 
dime 
and 
the 
diameter 
work 
as 
well.

Cheers,

Jonne.
ext 
Frank 
Xia 
wrote:
> 
Hi 
Soininen
>
> 
I 
think  
that 
"RADIUS 
Proxy 
Mobile 
IPv6" 
is 
another 
topic 
to 
consider 
for
> 
rechartering.
> 
http://tools.ietf.org/wg/netlmm/draft-xia-netlmm-radius-02.txt
>
> 
It 
is 
necessary 
mechanism 
when 
deploying 
PMIPv6 
using 
RADIUS 
as 
AAA 
protocol.
>
> 
In 
fact, 
the 
corresponding 
document, 
Diamter 
Proxy 
Mobile 
IPv6, 
is 
also  
being 
> 
discussed  
as 
a 
rechartering 
item 
in 
DIME 
WG.
> 
http://tools.ietf.org/wg/dime/draft-korhonen-dime-pmip6-03.txt.
>
> 
BR
> 
Frank
>
> 
----- 
Original 
Message 
----- 
> 
From: 
"Soininen 
Jonne 
(NSN 
FI/Espoo)" 
<jonne.soininen@nsn.com>
> 
To: 
<netlmm@ietf.org>
> 
Sent: 
Wednesday, 
February 
27, 
2008 
4:34 
PM
> 
Subject: 
[netlmm] 
About 
the 
Agenda 
for 
the 
meeting 
- 
your 
input 
is 
needed
>
>
> 
Hello 
everybody,
>
> 
I 
didn't 
have 
the 
possibility 
before 
today 
to 
combine 
the 
agenda, 
though 
I
> 
kind 
of 
knew 
what 
to 
expect. 
I 
think 
we 
have 
a 
problem 
for 
which 
I 
would
> 
like 
to 
ask 
for 
your 
help.
>
> 
First 
of 
all 
the 
proposed 
skeleton 
is 
the 
following:
>
> 
Network-based 
Local 
Mobility 
Management 
(NetLMM)
>
> 
---------------------------------------------------------
> 
TUESDAY, 
March 
11, 
2008
> 
0900-1130 
Morning 
Session 
I
>
> 
Chairs: 
> 
Jonne 
Soininen 
<jonne.soininen@nsn.com>
> 
Vidya 
Narayanan 
<vidyan@qualcomm.com>
>
> 
---------------------------------------------------------
> 
PRELIMINARIES
> 
Agenda 
review
> 
Blue 
sheets
> 
Notes 
and 
Jabber 
scribe
> 
WG 
status
>
> 
WG 
DRAFT 
DISCUSSIONS
>
> 
Topic: 
Proxy 
Mobile 
IPv6
> 
Draft: 
draft-ietf-netlmm-proxymip6-11.txt
>
> 
Topic: 
IPv4 
Support 
for 
Proxy 
Mobile 
IPv6
> 
Draft: 
draft-ietf-netlmm-pmip6-ipv4-support-02.txt
>
> 
Topic: 
Interface 
between 
a 
Proxy 
MIPv6 
Mobility 
Access 
Gateway 
and 
a 
Mobile
> 
Node
> 
Draft: 
draft-ietf-netlmm-mn-ar-if-03
>
> 
POSSIBLE 
NEW 
WORK 
ITEMS
>
> 
Presentations 
of 
the 
possible 
new 
work 
items
>
> 
RECHARTERING 
DISCUSSIONS
>
> 
NEXT 
STEPS 
and 
WRAP 
UP
> 
---------------------------------------------------------
> 
So 
we 
have 
basically 
2.5 
hours 
to 
spend, 
and 
we 
_have 
to_ 
discuss 
the
> 
current 
WG 
drafts, 
and 
get 
to 
understand 
what 
are 
we 
doing 
going 
forward.
> 
The 
emphasis 
of 
the 
work 
has 
to 
be 
on 
these 
two 
things.
>
> 
I 
have 
listed 
the 
following 
requests 
for 
presentations 
(the 
order 
is 
not
> 
important):
>
> 
-Multiple 
Interface 
Support 
with 
PMIPv6 
(15 
Min) 
- 
Vijay
>  
(draft-devarapalli-netlmm-multihoming-02.txt)
>
> 
-PMIPv6 
Heartbeat 
Mechanism 
(10 
Min) 
- 
Vijay
>  
(draft-devarapalli-netlmm-pmipv6-heartbeat-01.txt)
>
> 
-PMIPv6 
and 
MIPv4 
interactions 
(10 
min) 
- 
Vijay
>
> 
-Multihoming 
Scenarios 
(10 
min) 
- 
Ahmad
>
> 
-GRE 
keying 
(5 
min) 
- 
Ahmad
>
> 
-Route 
Optimization 
(10 
min) 
- 
Christian
>
> 
-Inter-MAG 
Route 
Optimization 
(10 
min) 
Ashutosh
>
> 
-Inter-technology 
handover 
extensions 
(10 
min) 
- 
Marco
>
> 
-PMIPv6 
support 
Transient 
CoA 
Registration 
(10 
min) 
- 
Ahmad
>  
draft-muhanna-netlmm-pmipv6-support-transient-coa-00.txt
>
> 
-Proxy 
Network 
Mobility 
(10 
Min) 
- 
John
>
> 
-Secondary 
Binding 
Cache 
Entries 
for 
PMIP 
(10 
min) 
- 
Oliver
>  
draft-blume-netlmm-secondary-bce-proxymip6ho-00.txt
>
> 
-Multiple 
interface 
support 
(10 
min) 
- 
Mohana
>  
draft-jeyatharan-netlmm-multi-interface-ps-01.txt
>
> 
-Proxy 
Mobile 
IPv6 
indication 
and 
discovery 
(10 
min) 
- 
Basavaraj
> 
draft-damic-netlmm-pmip6-ind-discover-03.txt
>
> 
And 
I'm 
pretty 
sure 
I 
forgot 
something 
(please 
remind 
me 
if 
I 
did).
>
> 
The 
problem 
is 
that 
this 
does 
not 
really 
fit. 
We 
cannot 
have 
all 
of 
these
> 
presentations 
and 
accomplish 
our 
main 
goal 
of 
the 
meeting. 
So, 
I 
think 
we
> 
have 
to 
compress 
and 
rethink 
the 
presentations.
>
> 
However, 
I 
see 
some 
patterns/groups 
(again 
the 
order 
is 
not 
of 
importance):
>
> 
Interaction
>  
-PMIP6-MIP4
>  
-PMIP6-MIP6 
(presented 
in 
earlier 
meeting)
>
> 
Multiple 
interface 
support/Multihoming
>  
-Vijay
>  
-Mohana
>  
-Ahmad
>  
-Marco?
>
> 
Route 
Optimization
>  
-Christian
>  
-Ashutosh
>
> 
Multiple 
COA 
Registration
>  
-Ahmad
>  
-Oliver
>
> 
Others
>  
-GRE 
keying 
(Ahmad)
>  
-Heart 
Beat 
(Vijay)
>  
-PMIP 
indication 
and 
discovery 
(Basavaraj)
>
> 
Could 
we 
do 
some 
grouping 
here 
or 
cooperation 
to 
get 
the 
different 
problems
> 
areas 
at 
least 
presented? 
In 
addition, 
I 
would 
think 
it 
would 
be 
good 
to 
get
> 
the 
items 
presented 
that 
it 
seems 
our 
"customers" 
like 
3GPP, 
3GPP2, 
and
> 
Wimax 
Forum 
expect 
us 
to 
get 
done. 
I 
think 
this 
is 
extremely 
important 
input
> 
for 
the 
rechartering 
discussion.
>
> 
Any 
ideas 
or 
suggestions?
>
> 
Cheers,
>
> 
Jonne.
>
> 
PS. 
I 
think 
we 
will 
let 
only 
the 
people 
enter 
the 
meeting 
room 
who 
have
> 
commented/reviewed 
the 
remaining 
WG 
items 
we 
have 
in 
the 
current 
charter...
> 
;)
>
> 
PS/2: 
Any 
volunteers 
for 
Jabber 
scribes 
and 
minute 
takers?
>
>  
 

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



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