ietf
[Top] [All Lists]

RE: Last Call: draft-jones-dime-3gpp-eps-command-codes (DiameterCommand Code Registration for Third Generation PartnershipProject (3GPP) Evolved Packet System (EPS)) to Informational RFC

2009-02-11 03:54:27
Cullen,

The current allocation policy is defined by RFC 3588, section 11.2.1
which indeed makes no distinction between permanent, standard commands
and vendor-specific command codes and requires IETF consensus for all.
This will be fixed by
http://www.ietf.org/internet-drafts/draft-ietf-dime-rfc3588bis-15.txt
but until this document is approved we are trying to answer the requests
coming from other SDOs (3GPP in this case) according to the existing
IANA registration process. 

Dan


-----Original Message-----
From: ietf-bounces(_at_)ietf(_dot_)org 
[mailto:ietf-bounces(_at_)ietf(_dot_)org] On 
Behalf Of Cullen Jennings
Sent: Wednesday, February 11, 2009 5:28 AM
To: ietf(_at_)ietf(_dot_)org
Subject: Re: Last Call: 
draft-jones-dime-3gpp-eps-command-codes (DiameterCommand Code 
Registration for Third Generation PartnershipProject (3GPP) 
Evolved Packet System (EPS)) to Informational RFC


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&dTa
g=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