One document matched: draft-smith-abfab-oidregistry-01.xml
<?xml version="1.0" encoding="US-ASCII"?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc strict="no"?>
<?rfc rfcedstyle="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2434 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2434.xml">
<!ENTITY I-D.ietf-abfab-gss-eap SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-abfab-gss-eap.xml">
]>
<rfc category="info" docName="draft-smith-abfab-oidregistry-01" ipr="trust200902">
<front>
<title abbrev="ABFAB Use Cases">Application Bridging for Federated Access Beyond web (ABFAB) OID Registry</title>
<author fullname="Dr. Rhys Smith" surname="Smith" initials="R">
<organization>Cardiff University</organization>
<address>
<postal>
<street>39-41 Park Place</street>
<city>Cardiff</city>
<code>CF10 3BB</code>
<country>United Kingdom</country>
</postal>
<phone>+44 29 2087 0126</phone>
<email>smith@cardiff.ac.uk</email>
</address>
</author>
<date year="2011" />
<area>Security Area</area>
<workgroup>ABFAB</workgroup>
<keyword>Internet-Draft</keyword>
<keyword>Federated Authentication</keyword>
<keyword>AAA</keyword>
<keyword>RADIUS</keyword>
<keyword>Diameter</keyword>
<keyword>GSS-API</keyword>
<keyword>EAP</keyword>
<keyword>SASL</keyword>
<abstract>
<t>
The IETF ABFAB working group has been assigned an OID arc by IANA. The goal of this document is to catalogue usage within the arc and the procedures for IANA to use to control the arc after the ABFAB working group has handed the arc over.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
IANA has assigned the IETF ABFAB working group an OID arc of 1.3.6.1.5.5.15 (iso.org.dod.internet.security.mechanisms.abfab). The goal of this document is to catalogue usage within the arc and the procedures for IANA to use to control the arc after the ABFAB working group has handed the arc over.
</t>
</section>
<section title="OID Registry">
<t>
OIDs in usage under this arc are to be passed to IANA when the ABFAB working group deems the arc sufficiently mature. This list is intended to be exhaustive.
</t>
<figure>
<artwork><![CDATA[
Prefix: iso.org.dod.internet.security.mechanisms.abfab (1.3.6.1.5.5.15)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 mechanisms A sub-arc containing ABFAB mechanisms
2 nametypes A sub-arc containing ABFAB GSS-API Name Types
]]></artwork>
</figure>
<figure>
<artwork><![CDATA[
Prefix: iso.org.dod.internet.security.mechanisms.abfab.mechanisms (1.3.6.1.5.5.15.1)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 gss-eap-v1 The GSS-EAP mechanism [I-D.ietf-abfab-gss-eap]
]]></artwork>
</figure>
<figure>
<artwork><![CDATA[
Prefix: iso.org.dod.internet.security.mechanisms.abfab.nametypes (1.3.6.1.5.5.15.2)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 GSS_EAP_NT_EAP_NAME [I-D.ietf-abfab-gss-eap]
]]></artwork>
</figure>
</section>
<section title="OID registration process">
Once we hand this over to IANA, what process should they use for assigning new OIDs.
</section>
<section title="Acknowledgements">
<t>
TODO
</t>
</section>
<section title="Security Considerations">
<t>
TODO
</t>
</section>
<section title="IANA Considerations">
<t>
TODO.
</t>
<t>
All applications for assigned numbers under the ABFAB OID arc should be reviewed. TODO - Review process? TODO - Mailing list? Guidance to IANA if not review process?
</t>
<t>
See <xref target="RFC2434"/>
</t>
</section>
</middle>
<back>
<section title="Other Related Arcs - REMOVE BEFORE FINAL VERSION">
<t>
There are also OIDs in usage under other private arcs. These are not intended to be passed to IANA, but are temporarily recorded here, purely for completeness. This section is intended to be removed for the final version of this I-D. Note that this list may not be exhaustive. TODO - remove this section before final draft.
</t>
<figure>
<artwork><![CDATA[
Prefix: iso.org.dod.internet.private.PADL.gssEap (1.3.6.1.4.1.5322.22)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 mechanisms
2 nameTypes
3 apiExtensions
Prefix: iso.org.dod.internet.private.PADL.gssEap.mechanisms
(1.3.6.1.4.1.5322.22.1)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 eap-aes128-cts-hmac-sha1-96
2 eap-aes256-cts-hmac-sha1-96
Prefix: iso.org.dod.internet.private.PADL.gssEap.nameTypes
(1.3.6.1.4.1.5322.22.2)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 principalName
Prefix: iso.org.dod.internet.private.PADL.gssEap.apiExtensions
(1.3.6.1.4.1.5322.22.3)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 inquireSecContextByOid
2 inquireCredByOid
3 setSecContextOption
4 setCredOption
5 mechInvoke
Prefix: iso.org.dod.internet.private.PADL.gssEap.apiExtensions.setCredOption
(1.3.6.1.4.1.5322.22.3.4)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 setRadiusConfigFile
2 setRadiusConfigStanza
3 setCredFlag
]]></artwork>
</figure>
<figure>
<artwork><![CDATA[
Prefix: iso.org.dod.internet.security.mechanisms.abfab.nametypes (1.3.6.1.5.5.15.2)
Decimal Name Description References
------- ---- ------------------------------------ ----------
0 Reserved Reserved
1 GSS_EAP_NT_EAP_NAME
]]></artwork>
</figure>
</section>
<references title="Normative References">
&rfc2434;
&I-D.ietf-abfab-gss-eap;
</references>
<references title="Informative References">
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 02:40:16 |