Hannes Tschofenig | 3 Jan 2008 12:17
Picon

[MEXT] [Fwd: [Dime] 2nd WGLC: Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction]

FYI

-------- Original Message --------
Subject: 	[Dime] 2nd WGLC: Diameter Mobile IPv6: Support for Network 
Access Server to Diameter Server Interaction
Date: 	Thu, 03 Jan 2008 12:04:59 +0100
From: 	Hannes Tschofenig <Hannes.Tschofenig <at> gmx.net>
To: 	dime <at> ietf.org

Hi all,

this message marks the issuance of the second working group last call 
(WGLC) on DIME's Internet Draft entitled "Diameter Mobile IPv6: Support 
for Network Access Server to Diameter Server Interaction" 
(draft-ietf-dime-mip6-integrated-07.txt). You may view this document at
http://tools.ietf.org/html/draft-ietf-dime-mip6-integrated-07

In August 2007 we initiated the 1st WGLC on 
draft-ietf-dime-mip6-integrated-05.txt, see
http://www1.ietf.org/mail-archive/web/dime/current/msg01940.html

Based on the feedback from the group version 6 and version 7 of the 
draft have seen some changes:
http://tools.ietf.org/rfcdiff?url2=http://tools.ietf.org/id/draft-ietf-dime-mip6-integrated-06.txt
http://tools.ietf.org/rfcdiff?url2=http://tools.ietf.org/id/draft-ietf-dime-mip6-integrated-07.txt

We would therefore like to initiate a short 2nd WGLC to ensure that all 
comments have been properly captured.

Please post comments and questions to the DIME mailing list no later 
(Continue reading)

George Tsirtsis | 4 Jan 2008 09:03

Re: [MEXT] MEXT interim meeting 7,8 feb 2007

Marcelo et.al.,

Are you planning to publish the agenda for the interim meeting in
advance? It might help people decide whether to come or not.

Thanks
George

On Dec 18, 2007 12:20 PM, marcelo bagnulo braun <marcelo <at> it.uc3m.es> wrote:
> Hi,
>
> We are finally organizing the MEXT interim meeting.
>
> The information is included below.
>
> MEXT interim meeting
>
> DATE:
> 7,8 feb 2007
>
> Location:
> University Carlos III de Madrid
> Escuela Politecnica Superior
> Av. Universidad 30
> 28911 - Leganes
> Madrid, SPAIN
>
> Goal of the meeting:
> The focus of the meeting would be the nemo ro work and other
> considerations for nemo global deployment.
(Continue reading)

marcelo bagnulo braun | 4 Jan 2008 17:29
Picon

Re: [MEXT] MEXT interim meeting 7,8 feb 2007

Hi,

i would expect that for the mid jan we will be able to publish a  
draft agenda

Regards, marcelo

El 04/01/2008, a las 9:03, George Tsirtsis escribió:

> Marcelo et.al.,
>
> Are you planning to publish the agenda for the interim meeting in
> advance? It might help people decide whether to come or not.
>
> Thanks
> George
>
> On Dec 18, 2007 12:20 PM, marcelo bagnulo braun  
> <marcelo <at> it.uc3m.es> wrote:
>> Hi,
>>
>> We are finally organizing the MEXT interim meeting.
>>
>> The information is included below.
>>
>> MEXT interim meeting
>>
>> DATE:
>> 7,8 feb 2007
>>
(Continue reading)

Davis, Terry L | 4 Jan 2008 18:59
Picon
Favicon

RE: [MEXT] MEXT interim meeting 7,8 feb 2007

Marcelo

I will be making flight and hotel reservations later today for the
interim meeting.  Looking forward to the meeting.

Take care

Terry L Davis, P.E
Boeing Technical Fellow
Aircraft Network and Security Architecture & Strategy
Engineering Core - Avionics
Boeing Commercial Airplanes

Phone:  206-280-3716
Email:   Terry.L.Davis <at> Boeing.com> -----Original Message-----

> From: George Tsirtsis [mailto:tsirtsis <at> googlemail.com]
> Sent: Friday, January 04, 2008 12:04 AM
> To: marcelo bagnulo braun
> Cc: Julien Laganier; mext <at> ietf.org
> Subject: Re: [MEXT] MEXT interim meeting 7,8 feb 2007
> 
> Marcelo et.al.,
> 
> Are you planning to publish the agenda for the interim meeting in
> advance? It might help people decide whether to come or not.
> 
> Thanks
> George
> 
(Continue reading)

Brian Haley | 8 Jan 2008 16:52
Picon
Favicon

Re: [MEXT] RE: Reliability of sending BRR by the HA?

Sorry for the late response, see inline.

Alexandru Petrescu wrote:
> marcelo bagnulo braun wrote:
>> Hi,
>>
>> i am trying to understand the impact of this in rfc3775 update
>>
>> I don't think that whether it is a good idea to use BRR from the HA is 
>> relevant for the discussion of RFC3775 update (it is of course 
>> relevant for the mext ml but not imho for this particular process of 
>> updating rfc3775)
>>
>> what imho is relavnt for the discussion of updating rfc3775 is whether 
>> rfc3775 is clear enough about whether HAs should send BRR or not

I don't think HA's have to support sending BRRs since they can't ever 
delete the MN binding, it really should only be useful for a CN that 
implements a cache-replacement policy that purges old bindings.

>> From the text of rfc3775 that Alex sent in his original posting, it 
>> seems that only CNs should send BRR and BE and not by the HA, so, is 
>> there any text in rfc3775 that can possibly create confusion about HAs 
>> using BRR or BEs? Does anyone has interpreted rfc3775 in the way that 
>> HAs should send BRR and BEs?
> 
> I will invite other implementers express whether it's clear or not who 
> sends BRR and BErr.
> 
> For my reading, there are some occurences about the possibility of HA
(Continue reading)

marcelo bagnulo braun | 8 Jan 2008 20:32
Picon

[MEXT] call for agenda items for mext interim meeting

Hi,

we are working on the agenda for the interim meeting. If some of you  
have some item that would like to be discussed, please let us know.

Regards, marcelo
Ken Laberteaux | 9 Jan 2008 22:35
Picon
Favicon

CFP--VehiculAr Inter-NETworking (VANET) 2008

ANNOUNCEMENT  and CALL FOR PAPERS

ACM VANET 2008

Vehicle to Vehicle -- Vehicle to Roadside -- Vehicle to Internet

The Fifth ACM International Workshop on VehiculAr Inter-NETworking

In conjunction with ACM MobiCom 2008
Date: To be announced
San Francisco, California, USA

Sponsored by ACM SIGMOBILE

http://www.sigmobile.org/workshops/vanet2008/

Important Dates (tentative):
Paper Submission Deadline: April 6th
Notification of Acceptance: June 6th
Camera-Ready Deadline: June 27th

The goal of this workshop is to present and discuss recent advances in 
the development of vehicular inter-networking (VANET) technologies. 
Based on short- and medium-range communication as well as on cellular 
systems, vehicular inter-networking will enable vehicular safety 
applications (including collision and other safety warnings) as well as 
non-safety applications (like real-time traffic congestion and routing 
information, high-speed tolling, mobile infotainment, and many others).

The creation of high-performance, highly reliable, highly scalable, 
(Continue reading)

marcelo bagnulo braun | 10 Jan 2008 10:10
Picon

[MEXT] next steps on rechartering

Hi,

The proposed next steps in the rechartering process are the following.
With this email, we ask people that have proposed new items to be  
included in the charter to send updated text based on the received  
feedback, clarifying questions and discussion so far. The deadline  
for proposed items text is sunday 13 feb.

Then we will post the list of proposed charter items and we leave 10  
days for discussing them, clarifying questions and so on.

Then, we will ask people to express their opinions one the relevance  
of the work, by ordering the proposed items based on the priority of  
the proposed work. Hopefully this would allow us to understand where  
the WG stands and pick up a few new items to include in the charter  
right away and the rest of the work can be considered in future  
rechartering events.

So, please send recharter item text before the 13 feb.

Regards, marcelo
Ahmad Muhanna | 10 Jan 2008 15:30
Favicon

RE: [MEXT] next steps on rechartering

Hi Marcelo,

Below is the Binding Revocation for IP Mobility recharter text after
receiving all feedback.

Binding Revocation for IP Mobility:
===================================

   Define a binding revocation mechanism for Mobile IPv6 and its
   extensions.  This mechanism can be used by any entity involved in the
   base Mobile IPv6 protocol or one of its extensions to request its
   corresponding entity to terminate either one, multiple or all binding
   cache entries.  This work will be a joint work with the NETLMM WG.

Regards,
Ahmad

> -----Original Message-----
> From: marcelo bagnulo braun [mailto:marcelo <at> it.uc3m.es] 
> Sent: Thursday, January 10, 2008 3:10 AM
> To: mext <at> ietf.org
> Cc: Julien Laganier
> Subject: [MEXT] next steps on rechartering
> 
> Hi,
> 
> The proposed next steps in the rechartering process are the following.
> With this email, we ask people that have proposed new items 
> to be included in the charter to send updated text based on 
> the received feedback, clarifying questions and discussion so 
(Continue reading)

marcelo bagnulo braun | 10 Jan 2008 16:37
Picon

Re: [MEXT] next steps on rechartering

Hi Ahmad,

after talking with the netlmm chairs, we agreed that we would remove  
the last sentence from the charter text, but still keep the netlmm on  
the loop

so the proposed text would be:

Binding Revocation for IP Mobility:
===================================

    Define a binding revocation mechanism for Mobile IPv6 and its
    extensions.  This mechanism can be used by any entity involved in  
the
    base Mobile IPv6 protocol or one of its extensions to request its
    corresponding entity to terminate either one, multiple or all  
binding
    cache entries.

Regards, marcelo

El 10/01/2008, a las 15:30, Ahmad Muhanna escribió:

> Hi Marcelo,
>
> Below is the Binding Revocation for IP Mobility recharter text after
> receiving all feedback.
>
>
> Binding Revocation for IP Mobility:
(Continue reading)


Gmane