EXPORT CONTROLLED (See note on cover page) Multi-Vendor Alliance to Develop an Open Standard...

EXPORT CONTROLLED (See note on cover page)

Multi-Vendor Alliance to Develop an Open Standard enabling Highly Mobile, Directional, High data rate,

Ad-Hoc Communications Networks

22 April 2010NRL

Advisory BoardAdvisory Board

© The Open Group - DirecNet™ 2010. All rights reserved.DirecNet™ is a trademark of The Open Group in the US and other countries.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. Seq. Violations of the export laws are subject to severe criminal penalties. Distribution of this document is restricted to US persons only. It shall not be disclosed further, exported or transferred in any manner to any other Foreign Person or any foreign country, without prior written approval of the Defense Trade Controls Licensing, U.S. Department of State.


2

Why the Formation of the DirecNet Advisory Board

The Advisory Board has been established to facilitate the goal of the National Technology Transfer Act and OMB Circular A-119 that “…encourages the participation of Federal government representatives in a voluntary consensus standards body thus increasing the likelihood that standards under development will meet both public and private sector needs.” *

* CIRCULAR NO. A-119 February 10, 1998



3

Non Attribution

What happens in the advisory board, stays at the advisory board.

Guidance is from the Advisory Board – not from a named person.



4

Advisory Board

Intro Ray Cole

DirecNet TF Agenda, Overview Dave Bryant

SDWG Status Keith Olds

BWG Summary Andy Hunton

Discussions Ray Cole - All



5

DirecNetTM

• Vision– The DirecNet™ Task Force will standardize directional,

IP-enabled, highly-mobile, ad hoc mesh networks through a validated open specification.

• Mission – The DirecNet™ Task Force will develop, validate and

publish a non-proprietary DirecNet™ open standard.

• Composition – The DirecNet™ Task Force was formed under the legal

umbrella of The Open Group – Membership consists of industry representatives and

elected advisors

© The Open Group - DirecNet™ 2010. All rights reserved.DirecNet™ is a trademark of The Open Group in the US and other countries


66

DirecNetTM Formation• DirecNetTM multi-vendor alliance formed in July 2006

• Open, nonproprietary standard under development by recognized leaders in the development of military communications systems

• Members:

– BBN (Associate)

– BAE Systems

– The Boeing Company

– Cubic Defense Applications

– General Dynamics (Associate)

– Harris

– ITT Industries

– Elbit America

– L-3 Communications

– Northrop Grumman

– Raytheon

– Rockwell Collins

– Viasat (Associate)

• Open specification hosted by The Open Group



7


DirecNet™ Task Force Organization

Ray Cole (NRL)

Dave Bryant (Boeing)Dave Laney (Cubic)

John (Jay) Spaulding, Director (OpenGroup)

Keith Olds (Harris)Rachel Rivera (RC)

Andy Hunton (BAE)Howard Elowitz (Raytheon)


8March 22, 20078

DirecNetTM

• DirecNetTM enables linking of fixed and mobile platforms via self-organizing networks sharing near real time information throughout the BattleSpace



Wireless Cluster(Hub & Spoke)

Where DirecNet Fits in the Big Picture

JTRS or OtherCluster

High Speed IP Packet Routers

DirecNet

Wireless Cluster(Hub & Spoke)

DirecNet Goal: Emulate Fixed Internet Trunk Lines & Routing Infrastructure

Internet

Mil

itar

y M

ob

ile

Infr

astr

uc

ture

Radio LinkTrunk Lines

Ground Entry PointTo GIG

Civ

ilia

n F

ixe

d I

nfr

astr

uct

ure

Fiber OpticTrunk Lines

Intra-TFNetworks

Link-16 or other Network

High Capacity Backbone

Transition


10

DirecNetTM Goals

• Assured Multi-Vendor Interoperability• Increased User Data throughput (Gbps)• Long range connectivity• Enhanced Spectrum Efficiency – Increased Node

Density• Ad-Hoc Networking• IP Enabled• Beyond Line-of-Sight operation, Relay functions• Enable new operational capabilities• Open industry standard encouraging competition,

ensuring affordability• Provide secure, timely access to pertinent data



11March 22, 200711

Operational Concept

Design Objectives:• Maximize spectrum reuse • No fixed infrastructure• Network capacity scales with

users• Automated in-band and out-of-

band neighbor discovery •Cannot compromise probability of detection in the neighbor discovery process

• Decentralized rule-based ad hoc topology management

•Dynamic bandwidth allocation• Supports multiple data rates• Every node an IP router• Commercial practice layer 3

networking• No single point of failure

Tier 1

Tier 2

Tier 3

Sensor data

CONUS

FAB-T, SATCOM

DirecNet

DirecNet

HMMV

Local Area Networks

Ground troops

Weapon

DirecNet

GIG


GEP to GIG


Specification Development Working Group

Advisory Board Report April 22, 2010


Agenda

• Review PHY Document Comment Status• Data Link Layer Document Status


MACS

ecu

rity

Man

agem

ent

Wav

efo

rm M

anag

emen

t

Mobile Ad Hoc Networking

Logical Link Control

Dat

a S

tru

ctu

res

ProductCertification Documents

Product 1

…

Fu

nct

ion

al D

escr

ipti

on

Sys

tem

Req

uir

emen

tsReference Documents

Ove

rvie

w a

nd

Arc

hit

ectu

re D

ocu

men

t Interoperability Requirements Documents

NDTRANSEC

MAC

BE

Data MAC

… …

…

Product 2

Product 3

Product NPHYs

Standards DocumentsCurrentSDWG Focus

Submitted for Member Review

EXPORT CONTROLLED (See note on cover page)DirecNet StandardReference System Diagram

Rev 8

MANET

MEDIAACCESS

PHYSICAL

WA

VE

FO

RM

MA

NA

GE

ME

NT

SE

CU

RIT

YM

AN

AG

EM

EN

T

21

5

6

18

14

24

2

8

1 3

19

9

25

4

2223

LOGICALLINK

7

15

13

12

16

20

10 11

17

Intra-Node Internal Interface External Interface

Inter-Node Internal Interface

Interface Legend

From External Interface Only

The DirecNetTM Reference Architecture Maps 213 requirements from the Functional Description Document to process blocks and interfaces which are defined in the Interoperability Standard Documents

Overview and Architecture Document

• Defines the Reference Architecture

• Interfaces• Functions

• Provides a “Roadmap” through the standards documents

DirecNetTM Reference Architecture


Physical Layer Document Status


PHY Review CommentsSDWG Response

• 32 comments were received from the member companies

• 26 have been dispositioned by the SDWG– 14 resulted in document changes– 13 did not require a document change

• 6 required additional effort– 1 returned for clarification– 5 have require additional technical study to

complete the SDWH response


Study Areas Raised by the Comments

• PHY Layer Overhead Discussions– Overhead for linearization and transmitter

settling– Overhead for equalizer training– Overhead for Doppler compensation and

frequency estimation– Support for real-time and post-processing

modems

• Power efficiency of pulse shaped OQPSK vs. QPSK– Reconciliation of contradictory study results


PHY Overview


Modulation Trade Space

Single Carrier Multiple Carrier (OFDM)

Spread Spectrum Minimum BW

Contiguous Channel BW

Non-ContiguousChannel BW

Modulation Formats

Modulation Formats

Spread Spectrum Minimum BW

Modulation Formats

Modulation Formats

Spread Spectrum

Minimum BW

Modulation Formats

Modulation Formats

BPSKQPSK16 QAM64 QAMOther

BPSK

BPSKTrade results depend on channel conditions

Constant Envelope(Max Pwr Eff)

BPSKQPSK8PSKGMSKOther




PHY Definition


Data Rate Table

• Mandatory Channels for Interoperability– UHF, L-Band and S-Band

• 1.2 MHz

– C-Band and X-Band• 6.26 MHz

– Ku-Band and Above• 25 MHz

0.96 Msps 2.5 Msps 5.0 Msps 7.2 Msps 10.0 Msps 20.0 Msps 40.0 Msps 72.0 Msps 120.0 Msps 240.0 Msps 320.0 Msps

1.200 MHz 3.125 MHz 6.25 MHz 9.00 MHz 12.5 MHz 25.0 MHz 50.0 MHz 90.0 MHz 150.0 MHz 300.0 MHz 400.0 MHzModulation Code RateBPSK 0.667 0.6 Mbps 1.7 Mbps 3.3 Mbps 4.8 Mbps 6.7 Mbps 13.3 Mbps 26.7 Mbps 48.0 Mbps 80.0 Mbps 160.0 Mbps 213.3 MbpsBPSK 0.750 0.7 Mbps 1.9 Mbps 3.8 Mbps 5.4 Mbps 7.5 Mbps 15.0 Mbps 30.0 Mbps 54.0 Mbps 90.0 Mbps 180.0 Mbps 240.0 MbpsQPSK 0.667 1.3 Mbps 3.3 Mbps 6.7 Mbps 9.6 Mbps 13.3 Mbps 26.7 Mbps 53.3 Mbps 96.0 Mbps 160.0 Mbps 320.0 Mbps 426.7 MbpsQPSK 0.842 1.6 Mbps 4.2 Mbps 8.4 Mbps 12.1 Mbps 16.8 Mbps 33.7 Mbps 67.4 Mbps 121.3 Mbps 202.1 Mbps 404.2 Mbps 538.9 Mbps16 QAM (APSK) 0.667 2.6 Mbps 6.7 Mbps 13.3 Mbps 19.2 Mbps 26.7 Mbps 53.3 Mbps 106.7 Mbps 192.0 Mbps 320.0 Mbps 640.0 Mbps 853.3 Mbps16 QAM 0.842 3.2 Mbps 8.4 Mbps 16.8 Mbps 24.3 Mbps 33.7 Mbps 67.4 Mbps 134.7 Mbps 242.5 Mbps 404.2 Mbps 808.4 Mbps 1077.9 Mbps64 QAM 0.667 3.8 Mbps 10.0 Mbps 20.0 Mbps 28.8 Mbps 40.0 Mbps 80.0 Mbps 160.0 Mbps 288.0 Mbps 480.0 Mbps 960.0 Mbps 1280.0 Mbps64 QAM 0.842 4.9 Mbps 12.6 Mbps 25.3 Mbps 36.4 Mbps 50.5 Mbps 101.1 Mbps 202.1 Mbps 363.8 Mbps 606.3 Mbps 1212.6 Mbps 1616.8 Mbps256 QAM 0.667 5.1 Mbps 13.3 Mbps 26.7 Mbps 38.4 Mbps 53.3 Mbps 106.7 Mbps 213.3 Mbps 384.0 Mbps 640.0 Mbps 1280.0 Mbps 1706.7 Mbps256 QAM 0.842 6.5 Mbps 16.8 Mbps 33.7 Mbps 48.5 Mbps 67.4 Mbps 134.7 Mbps 269.5 Mbps 485.1 Mbps 808.4 Mbps 1616.8 Mbps 2155.8 Mbps

BR-2 BR-10.71 BR-21.42 BR-44.73 BR-137 BR-274

Symbol Rate

Channel Bandwidth

Burst Data Rate

CDL Basic Rates


Data Link Layer Document Status


Data Link Layer Document Status1 INTRODUCTION 3

2 TABLE OF CONTENTS 9

3 LIST OF FIGURES 11

4 LIST OF TABLES 11

5 SCOPE 12

6 PURPOSE 13

7 OVERVIEW 14

8 REFERENCES 15

9 GLOSSARY 16

9.1 Definitions 16

9.2 Abbreviations and acronyms 18

9.3 Conventions 19

10 DIRECNET CONTEXT 21

11 LINK LAYER CONTEXT 23



12 LOGICAL LINK CONTROL SUBLAYER FUNCTIONS 24

12.1 LOGICAL LINK CONTROL OVERVIEW 24

12.1.1 Node State 24

12.1.2 Neighborhood Management 24

12.1.2.1 Neighborhood Member State Machine 24

12.1.3 In-band Control 28

12.2 NEIGHBOR DISCOVERY 28

12.2.1 Tightly Coupled In-band Neighbor Discovery

12.2.2 Tightly Coupled Out-of-band Neighbor Discovery

12.2.3 Loosely Coupled Neighbor Discovery

12.3 NEIGHBORHOOD CONNECTIVITY MANAGEMENT 29


Data Link Layer Document Status12.4 Link Establishment 29

12.4.1 Message Types 29

12.4.2 State Machine 30

12.4.3 Nominal Link Establishment Vignettes 31

12.5 Link Maintenance 35

12.5.1 Power Control and Rate Adaptation 35

12.5.2 Outage Management/Link Recovery 37

12.7.1 Link Loss Detection

12.7.2 Link Recovery

12.5.3 Position Tracking 37

12.5.4 Demand Assessment – Throughput 37

12.6.1 Link Tear Down 38

12.6.2 Reuse Maintenance 38

12.6.3 Interference Detection 38

12.5 Neighbor Information Distribution 38

12.8 Half Duplex Links (EMCON)



13 MEDIUM ACCESS CONTROL FOR THE BE-DN PHY39

13.1 MAC Control Plane 3913.1.1 TDD Operation 3913.1.2 TDMA Framing Definition 3913.1.2.1 Link Layer Timing 3913.1.2.2 Time Slot Control 3913.1.2.3 Transmit Slot Timing 3913.1.2.4 Receive Window Timing 3913.1.3 Multiple Access 3913.1.4 Demand Assignment 3913.1.5 Radio Resource Scheduling 3913.1.5.1 Time/Beam Scheduling 3913.1.5.2 Frequency Scheduling 3913.1.5.3 Modulation Scheduling 3913.1.5.4 Power Scheduling 3913.1.5.5 Multi-Carrier Tx/Rx Schedule Coordination 3913.1.6 TRANSEC Key Scheduling 39


Data Link Layer Document Status13.2 MAC Data Plane Functions for The BE-DN PHY 39

13.2.1 Data Encapsulation 3913.2.1.1 TDU Encapsulation 3913.2.1.2 TDU Header 3913.2.1.3 Packet Segmentation and Reassembly 3913.2.2 Distribute Packet Segments 4013.2.3 Link Layer Control Message Multiplexing 4013.2.4 Time Slot Packing 4013.2.5 TRANSEC Cover4013.2.6 TRANSEC Encryption 4013.2.7 TRANSEC Key Management 4013.2.8 Link Layer QOS 4013.2.8.1 Service Aware ARQ 4013.2.8.2 Transmit Prioritization 4014 PLATFORM DYNAMICS AND ON-THE-MOVE (OTM) OPERATION 4114.1 Maximum Aircraft Velocity 4114.2 Maximum Relative Aircraft Velocity 4114.3 Maximum Aircraft Altitude 4114.4 Minimum Air-to-Air Range 4114.5 Maximum Ground Vehicle Velocity 4114.6 Position Accuracy 4114.7 Attitude Accuracy 4115 PERFORMANCE 4215.1 Scalability 4215.2 Link Layer Latency 42


Logical Link Control


DirecNet Node Network States

ORPHAN

NETACQUISITION

NET MEMBER

RendezvousReceipt

HailReceipt

Tx Permission

WaveformStart

Network EntryCompleted

(link formed)

Loss of NW

SILENT WATCHSILENT WATCHSILENT WATCH

Go SilentCommandGo SilentCommand

Tx Permission

Hail Receiptw/ code

Go SilentCommand

Go SilentCommand

Exit SilentWatch

Net Acq. Failure

Last Link Lost

The DirecNet Link Layer Operation and Behavior is Organized Around a Node’s Role in the Network


Neighborhood Management


Neighborhood Member Relationships

Tracking

Link Establishment

Link Maintenance

Discovered &added to the Neighborhood

Connection Decision or INVITE rcvd

Link Established

Terminate link

• Each DirecNet “Local” Node defines a unique “Neighborhood”

• The Neighborhood consists of all nodes than may influence the Link Layer operation of the local node

• Connection possibilities

• Interference potential

• The Local Node maintains state on all of its neighborhood’s members

• Neighborhood member state defines the protocols and operations conducted between the local node and the Neighborhood Member Node


Neighborhood Member State Machine

Identified

Blocked

Invited Inviting

Poor Neighbor

GoodNeighbor

Countered


Link Layer Protocol Definition


COUNTERED

INVITED

INVITING

INVITED_1

INVITED_2

BLOCKED

INVITING_1

INVITING_2COUNTERED_1

POOR

NC

M r

eque

sts

conn

ect

ion

to p

eer

Neighbor feedback

INVITE_REJECT or

INVITE_TERMINAT

E

IDENTIFIED

Good INVITE

Bad INVITECOUNTERED_2

Bad INVITE

Bad INVITE

Bad INVITE or Timeout

Timeo

ut

Rejected INVITE

INVITE_REPLY

Timeout

INVITE_REPLY

Good

COUNTER_INVIT

E or

good

INVIT

E

INV

ITE

_R

EJE

CT

or

INV

ITE

_T

ER

MIN

AT

E

or b

ad

C

OU

NT

ER

_IN

VIT

E

Tim

eout

Good COUNTER_INVITE or Good INVITE

Timeout or

INVITE_TERMINATE

Good INVITE

Good INVITE

Bad INVITE

Link Establishment Protocol


Invite Channel Decision Flowchart

Start

Is Pending Neighbor Routable?

Route Invite through MANET layer

Use scheduled rendezvous time

END

Yes

No

In “Acquiring Network” or “Net Member” state

Connection Manager decides to make a new connection.

Invitation over MANET is preferred


DirecNet Schedule

TR Demos

Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

1.1 SDWG P&P1.2 Reqts Defn 1.3 Doc Struct1.4 IMP/IMS1.5 Implement Plan1.6 Val/Cert Plan 1.7 Change Plan1.8 FDD

2.1 DNStd 1: Overview/Arch 2.2 DNStd 10: PHY layer 2.3 DNStd 11: Data Link2.4 DNStd 20: Manet 2.5 DNStd 101: Management2.6 DNStd 102 Security :IMPLEMENTATION VALIDATION/CERTIFICATION CHANGES

2009 2010 2011 2012

SC Doc Approval First draft

Q1 Q22013

Q3Q4

Completed


Business Working GroupBusiness Working GroupAdvisory Board MeetingAdvisory Board Meeting

Washington DCWashington DCNRLNRL

22 April 201022 April 2010


39

BWG Agenda

• Old/Current Business– MILCOM– JTEN / NATS Meetings– CDL RFI / Industry Days– BAA Status

• New Business / Recommendations– Voice-of-the-Customer (VOC) Plan [AI 159]

• DirecNet Marketing Plan


Old / CurrentOld / CurrentBusinessBusiness


MILCOM DirecNetMILCOM DirecNetPanelPanel


42

MILCOM DirecNet Panel• Goal Expose the DoD community to the approach of the consortium

• Status Panel abstract submitted; awaiting acceptance from MILCOM UNCLASS panel committee

• Panel Abstract– There is an ever increasing need for a more robust, higher capacity and interoperable

communications infrastructure to support evolving DoD operational requirements. David Narkevicius of OSD NII states: “DoD is working to achieve communications interoperability, affordability, and incorporation of evolving technologies. The Department depends on reliable and flexible communications to support warfighter missions. In partnership with Industry, the Department is working to help develop future communications capabilities. Efforts like the DirecNetTM consortium teaming across industry are working to provide new communications capabilities offering interoperable, flexible, high bandwidth communications with a structure to optimize competition for cost savings to the Department.” This panel will discuss the DirecNetTM vision, waveform requirements drivers and development status. The focus is on a certifiable, non-proprietary, high capacity, directional mesh network RF-based waveform standard providing vendor-to-vendor and joint forces interoperability, while reducing overall life cycle cost.

• MILCOM 2010– San Jose Convention Center, CA– 31 Oct to 3 Nov 2010


43

MILCOM DirecNet Panel

• Panel agenda– Introduction (Dave Narkevicius) – 10 min– DirecNet Overview (Dave Bryant) – 10 min– Company 10 minute Overviews – 10 min x4– Q&A ~ 30 min

• Panel members (draft)– Moderator: Dave Narkevicius (OSD NII/DoD-CIO)– Dave Bryant (Boeing)– Tim Hughes (Raytheon)– Andrew Hunton (BAE Systems)– David Laney (Cubic)– Alan Brown (President, Open Group)

Hopefully Two Of The Panel Members Will Be From DoD


JTEN / NATS MeetingsJTEN / NATS MeetingsApril 6 & 8, 2010April 6 & 8, 2010


45

JTEN Meeting - DirecNet Objectives

1. Familiarize JTEN with the Task Force's technical objectives and multiple company organization.

2. Provide overview of DirecNet waveform to initiate assessment as a candidate solution for JALN high capacity backbone and transition capability.

3. Discuss potential DirecNet and industry participation in JTEN evaluation of future tactical networks.

4. Discuss JTEN representation on the DirecNet Government Advisory Board.

5. Generate an approach, in coordination with JTEN, for generating requirements for future tactical networks

– e.g.: “Voice of the Customer" process to be conducted by DirecNet

– Completed– Open 45

Date: April 6Location: Naval Research Labs; Wash DC

Participating In The JTEN Meeting Was A Great Success


46

NATS Meeting

• Highlights:– Government attendee questioned whether acquisition people could

participate due to the potential organizational conflict of interest (OCI) of assisting industry in generating standards or specifications.

COMMENT/ACTION: DirecNet has policies and procedures in place that should mitigate any OCI issues. Advice/assistance requested from the Advisory Board?

– QUESTION: What is the plan for DirecNet certification

ANSWER: Would be dependent on the level of assurance required by industry (combination of customer and vendor); explained the job of the Open Group is to ensure that the process is followed.

– QUESTION: Questioned the need for 1 Gbps waveform

ANSWER: This is the high end of the PHY layer standard and that lower data rates are available

• Multipath should be heavily considered in the standard

• NATS members were invited to attend future DirecNet Advisory Board meetings– Ron Broens will be joining the Advisory Board

Date: April 8Location: Lexington Park near Patuxent River

Naval Air Station, MD


CDL RFI /CDL RFI /Industry DaysIndustry Days


48

CDL RFI / Industry Exchange Days

• RFI– DirecNet submitted RFI Response on April 13th

• Industry Days – Kick-off on 4 May 2010 @ 0800 Hrs– Hanscom AFB; Bldg 1612, O’Neil Auditorium– 90 minute max briefing slot– Approval needed for 4th attendee

• Dave Bryant • Representative from SDWG• Representative from BWG• Jay Spaulding


49

CDL RFI / Industry Day- Strawman Plan -

• Phase I (12 months) ~ [ $ 3M ]– Complete standard– Conduct system analysis/trades in support of standards

development– Deliverables: DirecNet Rev 0 Standard & all associated

standards documents; Final Technical Report including all system/analysis trade-off results

• Phase II (12 months) ~ [ $ 4M ]– Develop DirecNet model & run simulations

• Focus on Link Layer and MANET Layer• Verify DirecNet meets network performance vs. JALN type

scenarios (traffic rates, congestion, packet error rates, network topologies)

– Deliverables: Final Tech Report; M&S Results• Phase III (12 months) ~ [ $10M ]

– Conduct critical risk reduction demonstrations• Prototype DirecNet terminals (modems, etc.) provided by

vendors• Conduct interoperability testing over limited set of scenarios• Conduct at baseband signal level

– Deliverables: Final Technical Report of findings and data results


BAA StatusBAA Status


51

BAA Status

• RFI Submittals– Dec 2010 ~ Template/format drafted and approved– Jan 2010 ~ All member companies submitted 1st round of BAA

responses

• Plan moving forward– NRL to work thru RFQs/negotiations with each company to set up

$10K contracts

• Effort– Meeting

• Presentations at NRL of classified scenarios

• Open discussions with DirecNet / government

– Classified documents distributed to contracted DirecNet companies


New Business/New Business/RecommendationsRecommendations


Voice of the CustomerVoice of the Customer& Market Plan& Market Plan


54

Market Plan for Creating Stakeholders

• Objective: Obtain high level DoD support for the DirecNet Standard

• Method: Utilize the VoC as a tool to obtain champions within the DoD customer community

• Plan:– Generate detailed customer matrix (key decision makers &

influencers) ~ 2 months [June]• DirecNet Member organization Bus Dev teams (in process)• Customers broken down:

– Requirements– Budget/Planners– S&T– Operators– Support– Acquisition

• Advisory Board review of customer matrix– Select most influential decision makers & set up customer

meetings/VoC interviews– Complete by next 6 months (Oct 2010)


Advisory BoardAdvisory BoardDiscussion and QuestionsDiscussion and Questions

NRLNRLWashington DCWashington DC

Quarterly Review MeetingsQuarterly Review Meetings21 January 201021 January 2010


Action Items

– Access to classified CONOPS for DoD Airborne Network • BAA submissions as reported earlier

• Status Update Ray Cole


Discussion Items1. NRL working mechanism for providing government classified scenarios to

DirecNet– What is best way for government to utilize DirecNet Task Force expertise?

• BAA or are there other areas or methods.

2. Deep dive/peer review of DirecNet progress– Review of PHY layer standard - March– In-process peer review of MAC and LLC layer work

• How would you suggest doing this?

3. Access to future operational unclassified scenarios that can’t be supported by existing systems to help supplement classified scenarios– Homeland Defense, Homeland Security– FEMA, State and local– Generic military scenarios mirroring classified scenariosStatus: Chris Gunderson working with BWG Chair

4. Status of Joint Aerial Layer ICD and AOA?

5. What other applications are there for DirecNet?

6. Advisory Board Comments, Recommendations, Actions for DirecNet Task Force

EXPORT CONTROLLED (See note on cover page) Multi-Vendor Alliance to Develop an Open Standard...

Documents

Transcript of EXPORT CONTROLLED (See note on cover page) Multi-Vendor Alliance to Develop an Open Standard...