200 likes | 675 Views
2. Scope. Produce draft conformance test methods from IEEE 1609.2-.4 Version 1 standards as a component of OmniAir Certification Program.Test methods will be based on:IEEE STD 1609.2:2006 (06 July 2006)IEEE STD 1609.3:2007 (20 April 2007)IEEE STD 1609.4:2006 (29 November 2006)TimelineWorking t
E N D
1. May 2, 2007 IEEE 1609 Working Group Meeting 1 IEEE 1609.2-.4 Test Method Update
2. 2 Scope Produce draft conformance test methods from IEEE 1609.2-.4 Version 1 standards as a component of OmniAir Certification Program.
Test methods will be based on:
IEEE STD 1609.2:2006 (06 July 2006)
IEEE STD 1609.3:2007 (20 April 2007)
IEEE STD 1609.4:2006 (29 November 2006)
Timeline
Working to complete in 4th quarter
3. 3 Approach Update Based on discussion at last WG meeting and further review:
No use of SAP’s, primitives in test methods
Combined black box testing
Standard &/or Test API(s) needed?
4. 4 Discussion Topics Test Model Update
Test System – Logical Components
Conformance Items
Questions
5. 5 Test Model Update Upper Tester (UT) Options
No UT (test coordination accomplished by operator with prompting from test system).
UT is an application residing on the SUT with no communication path for test coordination (test mode of operation).
UT is an application residing on the SUT utilizing in-band communication for test coordination (better test control than #1 or #2 options).
UT is an application residing on the SUT utilizing out of band communication for test coordination (less radio effects).
UT is an application residing external to the SUT utilizing the 1609.3 forwarding function (preferred for RSE & OBE).
6. 6 Test System – Logical Components
7. 7 Test System Components Test Control
Provides test coordination
Packet Sniffers
Observe data exchanges
COTS when available
Test Units
Interact with IUT/SUT during test
Traffic Units
For tests requiring background traffic (if necessary)
Certification Authority
Support security testing
8. 8 1609.2-.4 Conformance Items Will be selected from PICS
1609.2 PICS contains 234 items
108 mandatory
126 optional/conditional
1609.3 PICS contains 54 items
37 mandatory
17 optional/conditional
1609.4 PICS contains 43 items
41 mandatory
2 optional/conditional
9. 9 Questions 1609.2
1609.3
1609.4
Discussed at 2/07 WG meeting
Not included here, see previous presentation
10. 10 1609.2 Questions Certificate validity date range
Local applications
Root certificate store
Potential encrypted recipients certificate store
Revoked certificate store
Root certificate update
Other
11. 11 1609.2 Questions –Certificate Validity Date Range Did not find expiration date check in certificate processing for signed message transmission or reception (7.3).
Did not find expiration date check for encrypted message transmission (7.4.2).
Found expiration date check for encrypted message reception (7.4.3.1).
12. 12 1609.2 Questions –Local Applications In 7.2.2, root certificate store shall be available to local applications.
In 7.2.7, revoked certificate store available to applications hosted on the unit.
How does this apply to the 1609.3 forwarding function?
13. 13 1609.2 Questions –Root Certificate Store In 8.3.1, the security manager is identified as responsible for maintaining the root certificate store.
8.3.4 gives a description of how to update a root certificate.
No description found for adding a root certificate.
No description found for removing a root certificate.
In 7.2.2, conformance requires ability to store eight root certificates in the store. In PICS S124, the ability to store 32 is mandatory.
14. 14 1609.2 Questions – Encrypted Recipients Certificate Store In 7.2.1, distinction between cache and store is made.
In 7.2.6, potential encrypted recipients certificate store is also referred to as cache.
Per 7.2.6, the store shall include:
The last time that the certificate was used by the recipient [sic] (so that the certificate need only be checked against CRLs that have arrived since its last use).
Per 7.2.7 (Revoked Certificate Store), the time a CRL was received is not required to be stored.
See also 7.2.3, 7.2.4, and 7.3.3.7.
15. 15 1609.2 Questions –Other Generate Encrypted and Signed Message
PICS S9 status listed as S1,S7:M (S1,S5:M?)
Maintain CA certificate store
Per 7.2.3 this is cache not store
PICS S24 lists this as mandatory, but 7.2.3 uses may.
Maintain recently received message cache
PICS S26 lists this as mandatory, but 7.2.5 uses may.
Maintain potential encrypted recipients certificate store
PICS S27 status listed as S7:M (S5:M?)
Encode CAScope
PICS S109 status listed as :M (S61:M?)
Generate SecuredWSA
PICS S137 status listed as XXX:O (S19:M?)
16. 16 1609.3 Questions WSMP
Transmit Profile for Provider
Static SSID
Other
17. 17 1609.3 Questions –WSMP In PICS N1.10, suggest revising contents of value field.
Says “Data Length Verification sent to LCC” (sic)
Perhaps just “Verify Data Length and Send WSM to LLC”
In PICS N1.11, suggest revising contents of value field.
Says “Send WSM receipt”
Perhaps “Receive WSM from LLC and Send to Application”
18. 18 1609.3 Questions –Transmit Profile for Provider There is no PICS entry for Provider Transmit Profile Registration (6.2.1.1.2).
Entry for User Transmit Profile Registration is N2.8.
19. 19 1609.3 Questions –Static SSID From 6.2.1.1.1:
SSID. This is the identifier of the WBSS. The default value from the WME MIB is used.
In WME MIB, dot3Ssid is identified as read-write.
20. 20 1609.3 Questions –Other In 5.2, IPv6 support mandated with shall, PICS (N1.4) marked O.
In 5.3, UDP support mandated with shall, PICS (N1.5) marked O.
In 5.5, forwarding function support mandated with shall, PICS (N1.9) marked O.
21. 21 Questions / Discussion