 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
>>At some point soon, I guess we'll be releasing an update. It'd be good >>not to consume an experimental extension number in the process - how >>do we get a real one allocated? > > When an extension goes on Standards Track, it can get an extension > number. The registry requires "IETF consensus". Does this really imply a standards track RFC?
No. It means there must be an IETF Last Call.Russ