Re: [manet] Recharter Discussion

["Dearlove, Christopher (UK)" <[e-mail]>]

Chairs and WG

I just needed to touch base with the appropriate person here.

I can confirm that I’m aware of (am an inventor on) a patent application that is related to the area of encryption in an ad hoc network. At this point we’re only discussing whether we should work in this area, so issues of its use do not come up now.

(Do you need the number? I don’t have it to hand this second; however given that I’m not called Smith it’s quite easy to find - but see below.)

Having said that, I can now say that a requirement that some people I know have is that of concealing identity and topology/routing information. Which ad hoc routing protocols tend to freely distribute. That’s easy if you just use a shared secret key. That’s also fairly easy if everyone knows who everyone else is, and has symmetric or public keys for everyone else. But neither are ideal solutions (especially the latter that has serious overheads).

The combination of requirement and difficulty makes it a possible subject for the WG, if there’s enough support. But I do not expect anything security related, and especially crypto related, to be plain sailing. We would be strongly advised to get specialised input.

Beyond that of course there is encryption of traffic. An easier problem (at least unicast) in that it’s a standard IP problem. Key management is the issue. There are things related to the IBS draft that can help there, but no doubt others. (In fact I know of another using an alternative to that form of IBS.)

In short, we have some interest here. Do others?

As I noted above, I said patent application not hard to find. But it’s not the only one I’m a co-inventor in. (Though there aren’t many, about three). Another one might also be an area of WG interest, but one topic per email.

Christopher

--
Christopher Dearlove
Senior Principal Engineer
BAE Systems Applied Intelligence Laboratories
__________________________________________________________________________

T:  [phone]  |  E: [e-mail]<mailto:[e-mail]>

BAE Systems Applied Intelligence, Chelmsford Technology Park, Great Baddow, Chelmsford, Essex CM2 8HN.
www.baesystems.com/ai<http://www.baesystems.com/ai>
BAE Systems Applied Intelligence Limited
Registered in England & Wales No: 01337451
Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP

From: Stan Ratliff [mailto:[e-mail]]
Sent: 22 April 2016 16:51
To: Dearlove, Christopher (UK)
Cc: Justin Dean; [e-mail]
Subject: Re: [manet] Recharter Discussion


*** WARNING ***
This message originates from outside our organisation, either from an external partner or the internet.
Consider carefully whether you should click on any links, open any attachments or reply.
For information regarding Red Flags that you can look out for in emails you receive, click here<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Red%20Flags.pdf>.
If you feel the email is suspicious, please follow this process<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf>.
Hello WG,

Do we need to hold an interim meeting (via WebEX) to discuss? I'd like to get opinions on the list about that. We'll need a couple of weeks to schedule, but we can do that.

One other point inline:

On Fri, Apr 22, 2016 at 11:45 AM, Dearlove, Christopher (UK) <[e-mail]<mailto:[e-mail]>> wrote:
Multicast is the obvious top item. Lots of possible approaches, time to discuss.

Gateways for AODVv2 at Standard is obviously not possible since AODVv2 is going to be Experimental at most.

Management we did of course have an NHDP/OLSRv2 draft killed by AD. Which since NHDP/OLSRv2 us all we have (SMF excepted) that was a bit tricky.

I would have to make an IPR declaration to say some of what I might have to say about encryption. Not today.

Understood. But please remember - there's only about a 5-week gap now before the charter needs to be complete in order for the WG to meet in Berlin.

Regards,
Stan




Missing from the list is any work on OLSRv2 (or NHDP). MT-OLSRv2 is experimental. That would need implementation tests to advance to PS. Anyone interested in that (I’m not saying I can)?

More broadly on OLSRv2 there are various things that could be done, but what is really needed is people with a real application. Any that exist were frightened away from this group.

--
Christopher Dearlove
Senior Principal Engineer
BAE Systems Applied Intelligence Laboratories
__________________________________________________________________________

T:  [phone]<tel:%2B44%20%280%291245%20242194>  |  E: [e-mail]<mailto:[e-mail]>

BAE Systems Applied Intelligence, Chelmsford Technology Park, Great Baddow, Chelmsford, Essex CM2 8HN.
www.baesystems.com/ai<http://www.baesystems.com/ai>
BAE Systems Applied Intelligence Limited
Registered in England & Wales No: 01337451
Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP

From: manet [mailto:[e-mail]<mailto:[e-mail]>] On Behalf Of Justin Dean
Sent: 22 April 2016 16:07
To: [e-mail]<mailto:[e-mail]>
Subject: [manet] Recharter Discussion


*** WARNING ***
This message originates from outside our organisation, either from an external partner or the internet.
Consider carefully whether you should click on any links, open any attachments or reply.
For information regarding Red Flags that you can look out for in emails you receive, click here<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Red%20Flags.pdf>.
If you feel the email is suspicious, please follow this process<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf>.
*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.

I'll start things off by floating the draft re-charter which was presented in Prague.


The purpose of the MANET working group is to standardize IP routing protocol functionality suitable for wireless routing application within both static and dynamic topologies with increased dynamics due to node motion or other factors.



Approaches are intended to be relatively lightweight in nature, suitable for multiple hardware and wireless environments, and address scenarios where MANETs are deployed at the edges of an IP infrastructure. Hybrid mesh infrastructures (e.g., a mixture of fixed and mobile routers) should also be supported by MANET specifications and management features.



The MANET WG is responsible for the maintenance of OLSRv2, AODVv2, DLEP and NHPD. Of particular interest: border behavior between MANET networks and fixed IP network infrastructures, enhance AODVv2 gateway functionality; security enhancements, encryption security extensions for RFC5444.



The MANET WG will standardize a multicast MANET protocol framework based on previous work and lessons learned for scoped forwarding within MANET networks.  As part of this framework the WG will produce a well defined MANET multicast forwarding information base.



The WG will produce an informational draft outlining challenges and best practices for deploying and managing MANET networks.



The MANET WG will interact with the PIM working group on issues relating to the multicast work.  The WG will also pay attention to other IETF and IRTF work that is addressing topics related to MANET environments.



In summary, the WG will develop the following drafts:



MANET Management Document (Informational)

MANET Maintenance

 - RFC5444 Security extension (Standards)

 - Enhanced AODVv2 gateway extension (Standards)

MANET Multicast

 - Multicast FIB (Standards)





This will likely be considered too broad to pass.  We will likely need to cut some and focus the work.  For me personally I know I have the time and backing to work on the Multicast piece.



Justin

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

_______________________________________________
manet mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/manet