[MEXT] I-D Action:draft-ietf-mext-nemo-mib-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility EXTensions for IPv6 Working Group of the IETF.

	Title           : NEMO Management Information Base
	Author(s)       : S. Gundavelli, et al.
	Filename        : draft-ietf-mext-nemo-mib-06.txt
	Pages           : 44
	Date            : 2009-02-01

This memo defines a portion of the Management Information Base (MIB),
the network mobility support (NEMO) MIB, for use with network
management protocols in the Internet community.  In particular, the
NEMO MIB will be used to monitor and control a Mobile IPv6 node with
NEMO functionality.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-mib-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
MEXT mailing list
MEXT <at> ietf.org

Re: [MEXT] GRE support in DSMIPv6 - AD review

Folks, 

Just letting you know that DSMIPv6 is being updated now to address Pasi's
comments, regarding removing TLV and several other clarifications. I'm
hoping to get it out this week.

Hesham

[MEXT] Protocol Action: 'NEMO Management Information Base' to Proposed Standard

The IESG has approved the following document:

- 'NEMO Management Information Base '
   <draft-ietf-mext-nemo-mib-06.txt> as a Proposed Standard

This document is the product of the Mobility EXTensions for IPv6 Working 
Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-mib-06.txt

Technical Summary

  This memo defines a portion of the Management Information Base (MIB),
  the network mobility support (NEMO) MIB, for use with network
  management protocols in the Internet community.  In particular, the
  NEMO MIB will be used to monitor and control a mobile ipv6 node with
  NEMO functionality.

Working Group Summary

  The WG seems to agree in the need for this document and no-one
  seems to oppose to the document. 

Document Quality

  There are some vendors like Cisco working on this MIB
  development. In addition, KAME developers who implemented

Re: [MEXT] GRE support in DSMIPv6 - AD review

Fine. We will deal with this in the GRE draft as discussed
in netlmm.

Thanks
Sri

On Thu, 5 Feb 2009, Hesham Soliman wrote:

> Folks,
>
> Just letting you know that DSMIPv6 is being updated now to address Pasi's
> comments, regarding removing TLV and several other clarifications. I'm
> hoping to get it out this week.
>
> Hesham
>
>
>

[MEXT] I-D ACTION:draft-ietf-mext-nemo-ro-automotive-req-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Mobility EXTensions for IPv6 Working Group of the IETF.

	Title		: Automotive Industry Requirements for NEMO Route Optimization
	Author(s)	: R. Baldessari, T. Ernst, A. Festag, M. Lenardi
	Filename	: draft-ietf-mext-nemo-ro-automotive-req-02.txt
	Pages		: 25
	Date		: 2009-1-15
	
This document specifies requirements for NEMO Route Optimization
   techniques as identified by the automotive industry.  Requirements
   are gathered from the Car2Car Communication Consortium and ISO
   Technical Committee 204 Working Group 16 (CALM).  The document also
   overviews the current status of ETSI TC ITS, which is going to unify
   the approaches of these two automotive consortia in a single
   communication architecture.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-ro-automotive-req-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

[MEXT] Comments on draft-ietf-mext-nemo-ro-automotive-req-02.txt

Authors of draft-ietf-mext-nemo-ro-automotive-req-02.txt

Thanks for this new version of the draft, and for having included some
of my earlier comments.

I think there is more to which we seemed to agree.

In short:
-difficult to parse the text of HoA and CoA assignments
-link-local addresses facilitates only MR-to-MR communications (not LFN
  to LFN)
-figure 1 is the same as figure 3, redundancy.
-reference to 802.11p is outdated (at least D5 is more recent, there may
  be others).

Details follow.

draft:
> o  according to the current availability of infrastructure 
> connectivity, OBUs can use (at least) 2 types of globally routable 
> IPv6 addresses: an IPv6 address configured using standard IPv6 
> stateless address configuration from Router Advertisements sent by 
> RSUs connected to a network infrastructure and an IPv6 address 
> temporarily or permanently assigned to the vehicle belonging to a 
> home network and not varying while the vehicle changes its point- 
> of-attachment to the Internet.  The former globally routable IPv6 
> address is used as the NEMO Care-of Address (CoA) and the latter as 
> the NEMO Home Address (HoA).

Sounds as if the HoA is not globally routable - it is.

[MEXT] FW: New Version Notification for draft-ietf-mext-flow-binding-01

Folks, 

FYI, this is just a refresh of the draft because it expired. There will be a
new version before the meeting that addresses comments and updates. We
believe we'll be ready for WGLC after that.

Hesham

------ Forwarded Message
> From: IETF I-D Submission Tool <idsubmission <at> ietf.org>
> Date: Fri, 13 Feb 2009 21:42:52 -0800 (PST)
> To: Hesham Soliman <hesham <at> elevatemobile.com>
> Cc: Hesham Soliman <hesham <at> elevatemobile.com>,
> <nicolas.montavont <at> enst-bretagne.fr>, <niko <at> comnets.uni-bremen.de>,
> <koo <at> comnets.uni-bremen.de>
> Subject: New Version Notification for draft-ietf-mext-flow-binding-01
> 
> 
> A new version of I-D, draft-ietf-mext-flow-binding-01.txt has been successfuly
> submitted by Hesham Soliman and posted to the IETF repository.
> 
> Filename:  draft-ietf-mext-flow-binding
> Revision:  01
> Title:   Flow Bindings in Mobile IPv6 and Nemo Basic Support
> Creation_date:  2009-02-13
> WG ID:   mext
> Number_of_pages: 31
> 
> Abstract:
> This document introduces extensions to Mobile IPv6 and Nemo Basic

[MEXT] I-D Action:draft-ietf-mext-flow-binding-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility EXTensions for IPv6 Working Group of the IETF.

	Title           : Flow Bindings in Mobile IPv6 and Nemo Basic Support
	Author(s)       : H. Soliman, et al.
	Filename        : draft-ietf-mext-flow-binding-01.txt
	Pages           : 31
	Date            : 2009-02-13

This document introduces extensions to Mobile IPv6 and Nemo Basic
Support that allow nodes to bind one or more flows to a care-of
address.  These extensions allow multihomed nodes to take full
advantage of the different properties associated with each of their
interfaces.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mext-flow-binding-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
MEXT mailing list
MEXT <at> ietf.org

Re: [MEXT] Comments on draft-ietf-mext-nemo-ro-automotive-req-02.txt

Hi Alex,

Thanks for your comments, please see inline.

> 
> Thanks for this new version of the draft, and for having included some
> of my earlier comments.
> 
> I think there is more to which we seemed to agree.
> 

Yes, but it was not possible to apply all of the changes for the reasons you'll find below.

[...]
> 
> draft:
> > o  according to the current availability of infrastructure
> > connectivity, OBUs can use (at least) 2 types of globally routable
> > IPv6 addresses: an IPv6 address configured using standard IPv6
> > stateless address configuration from Router Advertisements sent by
> > RSUs connected to a network infrastructure and an IPv6 address
> > temporarily or permanently assigned to the vehicle belonging to a
> > home network and not varying while the vehicle changes its point-
> > of-attachment to the Internet.  The former globally routable IPv6
> > address is used as the NEMO Care-of Address (CoA) and the latter as
> > the NEMO Home Address (HoA).
> 
> Sounds as if the HoA is not globally routable - it is.
> 

Re: [MEXT] Comments on draft-ietf-mext-nemo-ro-automotive-req-02.txt

Hi Roberto, thanks for the reply.  I understand some could be included
some not.

More comments below.

Roberto Baldessari a écrit :
> [...]
>> draft:
>>> o  according to the current availability of infrastructure 
>>> connectivity, OBUs can use (at least) 2 types of globally 
>>> routable IPv6 addresses: an IPv6 address configured using 
>>> standard IPv6 stateless address configuration from Router 
>>> Advertisements sent by RSUs connected to a network infrastructure
>>>  and an IPv6 address temporarily or permanently assigned to the 
>>> vehicle belonging to a home network and not varying while the 
>>> vehicle changes its point- of-attachment to the Internet.  The 
>>> former globally routable IPv6 address is used as the NEMO Care-of
>>>  Address (CoA) and the latter as the NEMO Home Address (HoA).
>> Sounds as if the HoA is not globally routable - it is.
>> 
> 
> Was not intended. We can repeat 'globally routable', if this makes 
> things clearer.

YEs, it's clearer, thanks.

I think this clarification is needed to distinguish it from scenarios
where HoA is NATed (Scenario 3 Home Agent behind a NAT, of DS-MIPv6 draft).

>> "IPv6 address assigned to the vehicle belonging to a home network"