NIST Mobile BPR Kickoff Meeting – Notes, Actions & Next Steps

30 October 2014

1. Define intended audience of document

a. Acquisition

b. End users

c. Vendors

i. Other areas meeting missed?

1. Reporting

2. Interoperability

3. Field “trial and error” issues/fixes (lessons learned)

4. Software

a. 3rd party operating envts

b. O/S

c. Communication protocols (Ross M talk)

d. Connectivity issues

5. Architecture/configuration  what do we need the device to do?

a. Device mgmt., Proprietary templates – on backend, update 

watchlist, managing bandwidth, etc... 

2. Define scope of document

a. 1.1 vs. 2.0

b. Location of FAP/SAP/IAP?

i. ANSI/NIST ITL and hard reference in BPR

ii. BPR & ANSI/NIST (version control, other issues?)

iii. FAP/SAP/IAP are “profiles” and reference standards, i.e. WSQ, ANSI-NIST, 

AAMVA, etc...

iv. Put AP profiles in separate file and both ANSI/NIST ITL and BPR will reference

c. 1 document vs. multi-part document

d. Standard, recommendation, specification, de facto standard

e. Define scope of mobile

i. Size

1. Wearable, transportable, luggable, mixed, etc...

ii. Function

1. Mobile device + biographic/biometric collection, transmission, receive

2. Mobile computing environment that includes (2b i.) + other 

functionality such as GIS, Narcotic detection, explosives, electronic 

forms, etc...

3. Use cases/scenarios/taxonomy  Tabs 

a. Add previous DHS S&T use case/scenario document

b. Responsible: (Patty, Rick, Eric, Brad)

c. Ross M architecture information????

d. Add latent

4. Define role of Security in this document

a. Device management

b. Data retention/destruction

c. Store and forward

d. Operator authentication / single sign on

e.

5. Terminology consistency (Rick)

a. Use cases
NIST Mobile BPR Kickoff Meeting – Notes, Actions & Next Steps

30 October 2014

b. Scenarios

c. Applications

d. Configurations

e. Architectures

i. Add Ross M update

ii. Do we want to define workflows (impact on device mgmt., proprietary solutions 

and interoperability)????

f. Profile / application profile

g. Functions

h. capability

6. Update section on usability

a. What it is / WSABI

b. Desktop vs. mobile  not a direct port (add 1-2 sentences)

c. Iconography

7. Policy and privacy  reference that each agency/group is different

8. biometric specifications

a. Tune up

i. Finger

1. Add latent here?

2. Ann, Tom

ii. Face

1. Illumination?

2. Patrick

iii. Iris

1. Jim

b. Add

i. Voice

1. Possibly Patrick G.

2. Hiro?

3. Peter Higgins

4. SWG speaker

ii. DNA?

1. Brad

2. Pete Vallone

c. Future modalities - Do we want to explore others?

i. Tattoo?

1. Mae Ngan

ii. Hair

1. Brad

iii. Soft bio

1. Brad

iv. Associated data

1. Brad

9. Supporting verification of

a. User  biometric, document/token? (PIV, etc...)

b. Operator?

c. Responsible: Ryan T. 
NIST Mobile BPR Kickoff Meeting – Notes, Actions & Next Steps

30 October 2014

10. BPR “cleansing”

a. Strip out content that exists in ANSI/NIST ITL standard

b. Update references in document

c. Update technology, i.e. communications (sec 12.2)

d. Responsible: Brad, John MS, Rachel W

11. Do we want a section on and/or a list of lessons learned?

a. Should they be generalized?

b. As separate Appendix?

c. In use case/scenario descriptions?

d. ACTION – put out a call for mobile lessons learned

i. Army Center for lessons learned report

ii. Target users the group knows

e. Responsible: 

i. Brad to issue call

ii. Brian F. send to IAI yahoo groups

iii. Others poll/reach out to users

NOTE: Handling FAP/SAP tables as part of ANSI/NIST ITL process

- Timeframe to adopt update ~6 months

Schedule

1. Will try to release by 5th Nov  new look of BPR (Brad)

2. Group send inputs to Brad.wing@nist.gov

3. Working Group / Editing Meeting – 1st week of December?

a. Pull in DHS S&T Taxonomy, Use Cases, Scenario document

b. Terminology

4. Target next meeting in January/February 2015?