Hi Cullen,
This is what the forthcoming RFC3588bis will do. Vendor-specific
commands, like the 3GPP ones in this case, would be allocated on a
First Come, First Served basis by IANA. However, for this specific
request, RFC3588bis won't be ready/published soon enough.
Cheers,
Jouni
On Feb 11, 2009, at 5:27 AM, Cullen Jennings wrote:
My understanding is that this registry requires "IETF Consensus" as
defined in 2434. However, theses registration are being defined by
3GPP TS 29.272 which does not have IETF Consensus. If the DIME
community wishes to allow registrations like this, why not update
the IANA registration process to be "Specification Required"?
On Feb 5, 2009, at 7:17 AM, The IESG wrote:
The IESG has received a request from an individual submitter to
consider
the following document:
- 'Diameter Command Code Registration for Third Generation
Partnership
Project (3GPP) Evolved Packet System (EPS) '
<draft-jones-dime-3gpp-eps-command-codes-01.txt> as an Informational
RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to
the
ietf(_at_)ietf(_dot_)org mailing lists by 2009-03-05. Exceptionally,
comments may be sent to iesg(_at_)ietf(_dot_)org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.
The file can be obtained via
http://www.ietf.org/internet-drafts/draft-jones-dime-3gpp-eps-command-codes-01.txt
IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18081&rfc_flag=0
_______________________________________________
IETF-Announce mailing list
IETF-Announce(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf