1 NEMO: Requirements Analysis NEMO: Requirements Analysis draft-eddy-nemo-aero-reqs-02.txt draft-baldessari-c2ccc-nemo-req-01.txt draft-ng-nemo-ce-req-01.txt

2 AeronauticsC2CCCCE Req1 – Separability Ability to bypass RO for some traffic Req1 – Separability Ability to bypass RO for some traffic Req1 – Unmodified LFN LFN must not be modified Req2 – Multihoming Ability to use multiple access networks Req2 – MNN IPSec Ability for MNN to use IPSec for RO traffic Req2 – Processing Load No excessive processing for MR Req3 – Latency Must not block unoptimized flow Req3 – RO Security NO falsely claim MNP ownership Req3 – Security NO falsely claim MNP ownership NO tricking MR to send large packets Req4 – Availability No single point of failure Req4 – Privacy Protection Reveal MNP to only selected nodes Req5 – Packet Loss No additional packet loss due to RO Req5 – Multihoming Ability to use multiple access networks Req6 – Scalability Ability to handle 10,000 nodes Req6 –Sub-IP RO Coexistence Ability to choose NEMO-RO or sub-IP RO Req7 – Efficient Signaling Minimal additional signaling Req8 – Security Ability to use IPSec over RO; Data used for RO decision authenticable Req9 – Adaptability Work for new applications/protocols List of Requirements

3 AeronauticsC2CCCCE Req1 – Separability Ability to bypass RO for some traffic Req1 – identicalMissing – no conflict, probably can add to the draft Req2 – Multihoming Ability to use multiple access networks Req5 – identicalMissing – no conflict, probably can add to the draft Req3 – Latency Must not block unoptimized flow Missing – no conflict Req4 – Availability No single point of failure Missing – no conflict Req5 – Packet Loss No additional packet loss due to RO Missing – no conflict Req6 – Scalability Ability to handle 10,000 nodes Missing – no conflictMissing – no conflict, probably not necessary Req7 – Efficient Signaling Minimal additional signaling Missing – no conflictReq2 - implied Req8 – Security Ability to use IPSec over RO; Data used for RO decision authenticable Req2, Req3 –Req3 – cover RO’s security, not MNN’s use of IPSec Req9 – Adaptability Work for new applications/protocols Req6 – somewhat similar with coexistence Req1 – somewhat similar with unmodified LFN Aeronautics Perspective

4 AeronauticsC2CCCCE Req1 – identicalReq1 – Separability Ability to bypass RO for some traffic Missing – no conflict, probably can add to the draft Req8 – in partReq2 – MNN IPSec Ability for MNN to use IPSec for RO traffic Missing – no conflict, probably can add to the draft Req8 – in partReq3 – RO Security NO falsely claim MNP ownership Req3 Missing – no conflictReq4 – Privacy Protection Reveal MNP to only selected nodes Missing – no conflict Req2 – identicalReq5 – Multihoming Ability to use multiple access networks Missing – no conflict, probably can add to the draft Missing – probably not applicable Req6 –Sub-IP RO Coexistence Ability to choose NEMO-RO or sub-IP RO Missing – probably not applicable C2CCC Perspective

5 AeronauticsC2CCCCE Missing – maybe similar to Req9 (Adaptability) Missing – maybe similar to Req6 (Coexistence), Req2 (MNN’s IPSec) Req1 – Unmodified LFN LFN must not be modified Missing – maybe similar to Req7 (Efficient Signaling) Missing – no conflictReq2 – Processing Load No excessive processing for MR Req8 – in part, no DoS partReq3 – no DoS partReq3 – Security NO falsely claim MNP ownership NO tricking MR to send large packets CE Perspective

6 AeronauticsC2CCCCE Des1 – Configuration Simple to configure Des1 – MR-to-MR RO for MR-to-MR Des2 – Nesting Nesting of NEMOs Des2 – Nested-NEMO RO RO for Nested NEMO Des3 – System Impact Lower complexity Des3 – IntraNEMO RO RO within a merged NEMO Des4 – VMN Support Allow RO for VMNs Des5 – Generality Single solution for Aero, Automotive, CE List of Desired Features

7 AeronauticsC2CCCCE Des1 – Configuration Simple to configure MissingMissing – Probably needed Des2 – Nesting Nesting of NEMOs MissingDes2 – Des3 – System Impact Lower complexity MissingMissing – Probably not needed Des4 – VMN Support Allow RO for VMNs MissingMissing – Probably PMR as a VMN instead of allowing VMN Des5 – Generality Single solution for Aero, Automotive, CE Missing Comparison of Desired Features AeronauticsC2CCCCE Missing – is there plane to plane communications? Missing – probably use SubIPDes1 – MR-to-MR RO for MR-to-MR Des2 –MissingDes2 – Nested-NEMO RO RO for Nested NEMO Missing Des3 – IntraNEMO RO RO within a merged NEMO