Re: [MEXT] Aeronautical NEMO RO

Hi Alex,

> I have an overall question: is the absence of plane-to-plane
> communications scenarios from both the topology and solspace drafts - on
> purpose?  Or is it that nobody submitted input for it?
> 
> (In the solspace draft you analyze MNN-to-CN, MR-CN, MR-CR and MR-HA
>   communications, but not MR-to-MR communications.  In the topology
>   draft, MR-to-CN, points of attachment and ground equipment seem
>   needed.)
> 
> The IP mechanisms to achieve plane-to-plane communications may be easily
> developed, and they relate to the concept of NEMO network mobility and
> IPv6, and Mobile IPv6: may be categorized as optimal paths, the related
> IP techniques may be Route Optimization.
Air-to-air communication is of course existing, however, these applications often have broadcast semantics and, most importantly, are directly sitting on top of layer 2.

That is because they have no requirement for *multihop* communication. This is true for what is available today and even future ATS applications don't seem to have a requirement that goes beyond single-hop/broadcast-only communications (AFAIK).

The requirements document mentions air-to-air as (part of the) routing path for MNN-CN communications (see Des2 - Nesting). As this is not necessarily related to NEMO, it has been ommited.

Christian

> 
> Alex
> 
> >
> > Christian
> >
> >
> > -----Ursprüngliche Nachricht----- Von: IETF I-D Submission Tool
> > [mailto:idsubmission@ietf.org] Gesendet: Mittwoch, 9. September 2009
> > 14:47 An: Bauer, Christian Cc: Ayaz, Serkan; arnaud.ebalard@eads.net
> > Betreff: New Version Notification for
> > draft-bauer-mext-aero-solspace-00
> >
> >
> > A new version of I-D, draft-bauer-mext-aero-solspace-00.txt has been
> > successfuly submitted by Christian Bauer and posted to the IETF
> > repository.
> >
> > Filename:	 draft-bauer-mext-aero-solspace Revision:	 00 Title:
> > Solution Space for Aeronautical NEMO RO Creation_date:	 2009-09-09 WG
> >  ID:		 Independent Submission Number_of_pages: 29
> >
> > Abstract: Many potential solutions have been proposed for NEMO Route
> >  Optimization, although none has been adopted up to now.  This draft
> >  aims on evaluating the different approaches for the aeronautical use
> >  case.  At the end, a recommendation for the next steps is given.
> >
> >
> >
> > The IETF Secretariat.
> >
> >
> > _______________________________________________ MEXT mailing list
> > MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
> >
> 