Subversion Repositories oidinfo_new_design

Compare Revisions

Regard whitespace Rev 1 → Rev 2

/trunk/doc/OID-tutorial_fichiers/v3_outline_expanded.htm
0,0 → 1,1032
<html>
 
<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=ProgId content=PowerPoint.Slide>
<meta name=Generator content="Microsoft PowerPoint 9">
<link id=Main-File rel=Main-File href="../OID-tutorial.htm">
<link rel=Preview href=preview.wmf>
 
<script>
<!--
if( window.name != "PPTOtl" )
parent.location.href = "../OID-tutorial.htm";
//-->
</script>
<meta name=Robots content=NoIndex>
</head>
 
<body bgcolor=black text=white link=white vlink=white alink=white>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0036.htm');">Registration
Authorities<br>
for OID components</a></b></font></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0155.htm');">Protocols need to carry
names!</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Generic carrier protocols need names
for their contents</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Directory (X.500) protocols need names
for things they are trying to access</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>E-mail (X.400) protocols need names for
originator and recipient names</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0149.htm');">Historical contributions
to the naming problem</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>One of the first attempts at a naming
standard for data communication was X.121, used in X.25.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>32-bit Ethernet name allocation was
another important piece of standardisation.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Network Service Access Point addresses
in OSI (NSAP addresses) made an important contribution.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>ASN.1 definition of the Object
Identifier Tree in about 1986 was a seminal contribution.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>UUID naming mechanisms developed in the
1990s introduced new concepts to naming.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0150.htm');">Hierarchical v Central</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>I'm the Registration Authority, and
that's it (the Monolithic Approach).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>I will do my bit, you can add to
it<br>
(the Hierarchical Approach).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Let's use as much as possible of
existing naming<br>
(the Pragmatic Approach).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Marriages, marriages, marriages.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>For example, ISO Biometrics work uses a
centralised registration authority (Monolithic Approach), but has an Annex
that formally defines its allocations as part of an ASN.1 OID (Hierachical
Approach)</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0199.htm');">Character versus binary
naming</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Character versus binary protocols
remains an area of contention – preferred naming often follows this decision.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Current work on &quot;Fast Web
Services&quot; in ITU-T can be stated as &quot;binary encodings for Web
Services exchanges&quot;</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Fast Web Services may or may not gain
acceptance against XML (character-based) encodings for Web Services, but it
is a fight worth fighting! Please fight!</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Historically, ITU-T (CCITT before it)
has backed both binary *and* character-based naming horses.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0198.htm');">ASN.1 grasped the nettle</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width=20 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=2><font face=Arial size=2>The easy bit:</font></td>
</tr>
<tr>
<td colspan=2></td>
<td colspan=1><font face=Arial size=2>Combine the Hierarchical Approach and
the Pragmatic approach</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=2><font face=Arial size=2>The hard bit:</font></td>
</tr>
<tr>
<td colspan=2></td>
<td colspan=1><font face=Arial size=2>Long character strings versus obscure
binary representations</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=2><font face=Arial size=2>A lot of blood was spilled in 1985.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=2><font face=Arial size=2>Went for binary!!!! (In the encoding,
characters in the value notation – see later)</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=2><font face=Arial size=2><span style="mso-spacerun:
yes"> </span>OIDs are essentially binary encodings.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=2><font face=Arial size=2>Even when sent with XML they are
things<br>
like 0.2.693.57. etc – encoded in characters, but it is still binary!</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0212.htm');">Notation for OID values –
human-readable</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Early notation for OID values
(allocations) looked like:</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2><span style="mso-spacerun: yes">       
</span>{iso standard 8571 etc}</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>SNMP started the rot:<span
style="mso-spacerun: yes">  </span>use simply a character representation of
the encoding:<span style="mso-spacerun: yes">  </span>1.0.8571.etc for human
consumption.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>The change from &quot;ccitt&quot; to
&quot;itu-t&quot; in<br>
&quot;joint-iso-ccitt&quot; also caused problems.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>The numeric form is now accepted as
valid notation.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Names are now regarded as not
normative.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0200.htm');">X.400 and X.500</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>X.500 went for what became called
&quot;long-names&quot; – character-based.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>X.400 used both forms! (Differed a bit
in the 1984 vs. 1988 versions)</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2><span style="mso-spacerun:
yes"> </span>Major fight on introduction of &quot;short-names&quot; into
X.500 around 1988ish</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Accepted, but never really took off or
implemented.<span style="mso-spacerun: yes">  </span>Today, X.500
distinguished names are not considered &quot;long&quot; – compared, for
example with Certificate Revocation Lists (CRLs).</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0213.htm');">Navigating the tree</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>X.500 also added the concept that a
sub-arc might be identified by a pair of values (for example, organisational
unit and location), rather than just by a single value.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This is the principal difference (apart
from character v binary representation) between the X.500 use of the RH-name
tree concept and the ASN.1 use of the RH-name tree concept for the Object
Identifier tree.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0151.htm');">Moving to the Web</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Publication of naming allocations on
the Web is increasingly common but adds cost for an RA.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>The ITU-T OID description database is
an excellent example, with over 50,000 entries.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>OID repository: http://oid.elibel.tm.fr</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Automatic allocations (possibly using
Fast Web Services protocols) reduces the cost of running an RA.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>First done by IANA for ASN.1 OID
components for SNMP.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0152.htm');">ASN.1 Project and ITU-T
support</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>We live in interesting times!</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>An immense amount done already on the
module database and the OID registry.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Suggestions for automatic machine
access to ASN.1 modules from the database – Sun Microsystems involvement,
tool vendor agreement to provide clients.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Suggestions for automatic registration
of UUID values for an OID component (see later).</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0153.htm');">Enough of history and
futures – what of the NOW?</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>The revised X.660 and X.670 series
Recommendations are just that – revisions.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Incorporate amendments, update tables
and lists, and improve editorial clarity.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Don't bother to read them!</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0165.htm');">What are these
Recommendations? <br>
(Yuck, he's getting serious – time to walk out to my
main meeting!)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Sorry folks, but one slide per
Recommendation (could just be two or three for some!).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>I owe that to the authors that spent a
lot of time on the original work.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Walk out if you like, but this is the
guts of the presentation.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0214.htm');">General contents</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>(Sometimes) provides information on
Registration Hierarchical name trees.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Usually specifies procedures for the
operation of a Registration Authority.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Mainly defines procedures for
allocation under a specific ASN.1 Object Identifier arc.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Revision makes no real technical
changes – incorporates amendments, changes CCITT to ITU-T, clarifies, etc.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Makes UPU legitimate!</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0201.htm');">X.660 (ISO/IEC 9834-1)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Title:<span style="mso-spacerun:
yes">   </span>INFORMATION<span style="mso-spacerun: yes"> 
</span>TECHNOLOGY<span style="mso-spacerun: yes">  </span>–<span
style="mso-spacerun: yes">  </span>OPEN<span style="mso-spacerun: yes"> 
</span>SYSTEMS<span style="mso-spacerun: yes">  </span>INTERCONNECTION<span
style="mso-spacerun: yes">  </span>–<span style="mso-spacerun: yes"> 
</span>PROCEDURES FOR<span style="mso-spacerun: yes">  </span>THE<span
style="mso-spacerun: yes">  </span>OPERATION<span style="mso-spacerun: yes"> 
</span>OF<span style="mso-spacerun: yes">  </span>OSI<span
style="mso-spacerun: yes">  </span>REGISTRATION AUTHORITIES:<span
style="mso-spacerun: yes">  </span>GENERAL<span style="mso-spacerun: yes"> 
</span>PROCEDURES</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>A bad title!<span style="mso-spacerun:
yes">  </span>Still not quite settled!</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This describes the RH-Name tree, and
specifies general procedures for registration authorities in this area.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>These procedures are referenced from
other parts of the series.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0202.htm');">No X.661 (ISO/IEC 9834-2)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>FTAM Document type registration.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Many registrations within the ISO
profiles work.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>ISO work never supported by ITU-T.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Will not be revised, and not of
interest.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0203.htm');">X.662 (ISO/IEC 9834-3)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2><span style="mso-spacerun:
yes"> </span>Title:<span style="mso-spacerun: yes">   </span>INFORMATION<span
style="mso-spacerun: yes">  </span>TECHNOLOGY<span style="mso-spacerun:
yes">  </span>–<span style="mso-spacerun: yes">  </span>OPEN<span
style="mso-spacerun: yes">  </span>SYSTEMS<span style="mso-spacerun: yes"> 
</span>INTERCONNECTION<span style="mso-spacerun: yes">  </span>–<span
style="mso-spacerun: yes">  </span>PROCEDURES FOR<span style="mso-spacerun:
yes">  </span>THE<span style="mso-spacerun: yes">  </span>OPERATION<span
style="mso-spacerun: yes">  </span>OF<span style="mso-spacerun: yes"> 
</span>OSI<span style="mso-spacerun: yes">  </span>REGISTRATION
AUTHORITIES:<span style="mso-spacerun: yes">  </span>REGISTRATION<span
style="mso-spacerun: yes">  </span>OF<span style="mso-spacerun: yes"> 
</span>ASN.1 OBJECT IDENTIFIER ARCS FOR<span style="mso-spacerun: yes"> 
</span>JOINT<span style="mso-spacerun: yes">  </span>ISO<span
style="mso-spacerun: yes">  </span>AND<span style="mso-spacerun: yes"> 
</span>ITU-T<span style="mso-spacerun: yes">  </span>WORK</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This is an important Recommendation</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Provides the Registration of areas of
joint work with ITU-T and ISO.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>About 25 current allocations.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>ANSI remains the Registration
Authority.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Simple resolution from SG17 and SC6.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0204.htm');">No X.663 (ISO/IEC 9834-4)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>VT profile registration.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Many registrations within the ISO
profiles work.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>ISO work never supported by ITU-T.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Will not be revised, and not of
interest.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0205.htm');">No X.664 (ISO/IEC 9834-5)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2><span style="mso-spacerun:
yes"> </span>VT control object registration.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Many registrations within the ISO
profiles work.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>ISO work never supported by ITU-T.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Will not be revised, and not of
interest.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0206.htm');">X.665 (ISO/IEC 9834-6)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Title:<span style="mso-spacerun:
yes">   </span>INFORMATION<span style="mso-spacerun: yes"> 
</span>TECHNOLOGY<span style="mso-spacerun: yes">  </span>–<span
style="mso-spacerun: yes">  </span>OPEN<span style="mso-spacerun: yes"> 
</span>SYSTEMS<span style="mso-spacerun: yes">  </span>INTERCONNECTION<span
style="mso-spacerun: yes">  </span>–<span style="mso-spacerun: yes"> 
</span>PROCEDURES FOR<span style="mso-spacerun: yes">  </span>THE<span
style="mso-spacerun: yes">  </span>OPERATION<span style="mso-spacerun: yes"> 
</span>OF<span style="mso-spacerun: yes">  </span>OSI<span
style="mso-spacerun: yes">  </span>REGISTRATION AUTHORITIES:<span
style="mso-spacerun: yes">  </span>APPLICATION<span style="mso-spacerun:
yes">  </span>PROCESSES<span style="mso-spacerun: yes">  </span>AND<span
style="mso-spacerun: yes">  </span>APPLICATION<span style="mso-spacerun:
yes">  </span>ENTITIES</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Joint with ISO.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Will be formally revised, but defunct
and not of interest.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0207.htm');">X.666 (ISO/IEC 9834-7)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2><span style="mso-spacerun:
yes"> </span>Title:<span style="mso-spacerun: yes">   </span>INFORMATION<span
style="mso-spacerun: yes">  </span>TECHNOLOGY<span style="mso-spacerun:
yes">  </span>–<span style="mso-spacerun: yes">  </span>OPEN<span
style="mso-spacerun: yes">  </span>SYSTEMS<span style="mso-spacerun: yes"> 
</span>INTERCONNECTION<span style="mso-spacerun: yes">  </span>–<span
style="mso-spacerun: yes">  </span>PROCEDURES FOR<span style="mso-spacerun:
yes">  </span>THE<span style="mso-spacerun: yes">  </span>OPERATION<span
style="mso-spacerun: yes">  </span>OF<span style="mso-spacerun: yes"> 
</span>OSI<span style="mso-spacerun: yes">  </span>REGISTRATION
AUTHORITIES:<span style="mso-spacerun: yes">  </span>JOINT ISO AND ITU-T
REGISTRATION OF INTERNATIONAL<span style="mso-spacerun: yes"> 
</span>ORGANIZATIONS</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This is one of two Recommendations for
registration of International Organizations (see X.669 later).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Registers international organisations
under the ASN.1 joint ITU-T and ISO &quot;international-organisation&quot;
arcs, but also<span style="mso-spacerun: yes">  </span>defines X.500 and
X.400 naming of International Organisations</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>For X.400 it defines the PRMD and ADMD
concepts.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0215.htm');">X.667 (ISO/IEC 9834-8)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2><span style="mso-spacerun:
yes"> </span>Title:<span style="mso-spacerun: yes">   </span>INFORMATION<span
style="mso-spacerun: yes">  </span>TECHNOLOGY<span style="mso-spacerun:
yes">  </span>–<span style="mso-spacerun: yes">  </span>OPEN<span
style="mso-spacerun: yes">  </span>SYSTEMS<span style="mso-spacerun: yes"> 
</span>INTERCONNECTION<span style="mso-spacerun: yes">  </span>–<span
style="mso-spacerun: yes">  </span>PROCEDURES FOR<span style="mso-spacerun:
yes">  </span>THE<span style="mso-spacerun: yes">  </span>OPERATION<span
style="mso-spacerun: yes">  </span>OF<span style="mso-spacerun: yes"> 
</span>OSI<span style="mso-spacerun: yes">  </span>REGISTRATION
AUTHORITIES:<span style="mso-spacerun: yes">  </span>GENERATION AND
REGISTRATION OF UNIVERSALLY UNIQUE IDENTIFIERS (UUIDS)</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This is an important new
Recommendation, for approval at the March 2004 meeting of SG17.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>The history of UUID (GUID) work is
worth several slides on its own!</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>It involves Microsoft, IETF Draft RFCs
and the Open Group.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0216.htm');">Wow! A second slide!</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>UUIDs are extremely widely used, but
with no standard specifying them!</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>They are used in Bluetooth
specifications and in ISO/IEC/JTC1/SC37 BioAPI<span style="mso-spacerun:
yes">  </span>and CBEFF specifications (probably many others).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>References in the ISO work rely on this
Recommendation | International Standard</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0217.htm');">And a third!</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>UUIDs are quite big – 16 octets.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>They can be self-allocated on a
transient basis that guarantees uniqueness up to AD 3400, with allocations of
up to 10 million per second.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>They can also be allocated for
permanent identification.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Registration is not required, but
reduces probable uniqueness from 99% certain to 100% certain.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Can be used as ASN.1 OID components.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0209.htm');">Not X.668 (Not ISO/IEC
9834-9)</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>The one that got away.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Proposed as the RA Standard for
Biometric Registration.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>X.600 series had a lot to offer, and
much text from that series is being used.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>But decided to proceed with pure
ISO/SC37 Standard, as a second part of CBEFF.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Pity, but we tried!</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0210.htm');">X.669</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Title:<span style="mso-spacerun:
yes">   </span>INFORMATION<span style="mso-spacerun: yes"> 
</span>TECHNOLOGY<span style="mso-spacerun: yes">  </span>–<span
style="mso-spacerun: yes">  </span>OPEN<span style="mso-spacerun: yes"> 
</span>SYSTEMS<span style="mso-spacerun: yes">  </span>INTERCONNECTION<span
style="mso-spacerun: yes">  </span>–<span style="mso-spacerun: yes"> 
</span>PROCEDURES FOR<span style="mso-spacerun: yes">  </span>THE<span
style="mso-spacerun: yes">  </span>OPERATION<span style="mso-spacerun: yes"> 
</span>OF<span style="mso-spacerun: yes">  </span>OSI<span
style="mso-spacerun: yes">  </span>REGISTRATION AUTHORITIES:<span
style="mso-spacerun: yes">  </span>ITU-T REGISTRATION<span
style="mso-spacerun: yes">  </span>OF INTERNATIONAL ORGANIZATIONS
REGISTRATION</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This is one of two Recommendations for
registration of International Organizations.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This registers under the ITU-T arc to
ITU-T Members.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>The other (X.666) registers
organisations under the joint ISO/ITU-T arc.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>For totally historical reasons, this is
quite different from X.666 text.<span style="mso-spacerun: yes"> 
</span>X.666 is probably the more important and better text.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0211.htm');">X.670</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Title:<span style="mso-spacerun:
yes">   </span>PROCEDURES FOR REGISTRATION AGENTS OPERATING ON BEHALF OF
ORGANIZATIONS TO REGISTER ORGANIZATION NAMES SUBORDINATE TO COUNTRY NAMES.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This is a Recommendation for software
to register International Organizations under multiple countries (see X.671).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>It is believed that neither this
Recommendation nor X.671 has been implemented, and revision is a formality to
ensure coherence of the series.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0160.htm');">X.671</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Title:<span style="mso-spacerun:
yes">   </span>PROCEDURES FOR A REGISTRATION AUTHORITY OPERATING ON BEHALF OF
COUNTRIES TO REGISTER ORGANIZATION NAMES SUBORDINATE TO COUNTRY NAMES.</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>This is a Recommendation for the
operation of a Registration Authority in a country to register International
Organization names under that country name (see also X.670).</font></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>It is believed that neither this
Recommendation nor X.670 has been implemented, and revision is a formality to
ensure coherence of the series.</font></td>
</tr>
</table>
 
<p></p>
 
<p><font face=Arial size=2><b><a
href="javascript:parent.GoToSld('v3_slide0097.htm');">If you have lasted this
far, you have been very patient</a></b></font>
 
<table>
<tr>
<td width=5 nowrap></td>
<td width="100%"></td>
</tr>
<tr>
<td colspan=1></td>
<td colspan=1><font face=Arial size=2>Good-bye!</font></td>
</tr>
</table>
 
<p></p>
 
</body>
 
</html>