Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#187 closed defect (wontfix)

Use IANA-managed OIDs

Reported by: rlb@… Owned by: draft-ietf-trans-rfc6962-bis@…
Priority: major Milestone:
Component: to-be-decided Version:
Severity: - Keywords:
Cc:

Description

I disagree with the conclusion reached in #81, and agree with Russ that we should use an IETF-managed arc. Three octets is not worth the risk of using private identifiers in an IETF specification.

1.3.101.78 => 06 03 2B 65 4E
1.3.6.1.5.8.1 => 06 06 2B 06 01 05 08 01

Change History (6)

comment:1 Changed 5 years ago by rlb@…

  • Summary changed from User IANA-managed OIDs to Use IANA-managed OIDs

comment:2 Changed 5 years ago by rob.stradling@…

  • Component changed from client-behavior to to-be-decided

comment:3 follow-ups: Changed 5 years ago by rob.stradling@…

OIDs from the 1.3.101 arc are also being used by the CURDLE WG in draft-ietf-curdle-pkix.

Rich Salz mentioned that "Work is in progress to turn the arc over to IETF / IANA / someone-like-us." [1]

I propose that we close this ticket as "wontfix".

[1] https://mailarchive.ietf.org/arch/msg/spasm/656DnTC7JKjuyY8Z_U-FaBowWh8

comment:4 in reply to: ↑ 3 Changed 5 years ago by rob.stradling@…

Replying to rob.stradling@…:

I propose that we close this ticket as "wontfix".

In other words, let's continue to use the OIDs from the 1.3.101 arc.

comment:5 Changed 5 years ago by melinda.shore@…

  • Resolution set to wontfix
  • Status changed from new to closed

comment:6 in reply to: ↑ 3 Changed 5 years ago by rob.stradling@…

Replying to rob.stradling@…:

OIDs from the 1.3.101 arc are also being used by the CURDLE WG in draft-ietf-curdle-pkix.

Rich Salz mentioned that "Work is in progress to turn the arc over to IETF / IANA / someone-like-us." [1]

See this I-D:
https://datatracker.ietf.org/doc/draft-schaad-curdle-oid-registry

Should TRANS produce a similar document for the OIDs under the 1.3.101 arc that we're using?

Note: See TracTickets for help on using tickets.