IETF Logo Mail Archive

Re: Last Call: draft-jones-dime-3gpp-eps-command-codes (Diameter Command Code Registration for Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)) to Informational RFC

jouni korhonen <jouni.nospam@gmail.com> Wed, 11 February 2009 08:18 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDEEB3A69CF for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 00:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.305
X-Spam-Level:
X-Spam-Status: No, score=-2.305 tagged_above=-999 required=5 tests=[AWL=0.294, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TUbl2zU1Mowu for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 00:18:13 -0800 (PST)
Received: from mail-bw0-f161.google.com (mail-bw0-f161.google.com [209.85.218.161]) by core3.amsl.com (Postfix) with ESMTP id 6A75B3A67EE for <ietf@ietf.org>; Wed, 11 Feb 2009 00:18:13 -0800 (PST)
Received: by bwz5 with SMTP id 5so85911bwz.13 for <ietf@ietf.org>; Wed, 11 Feb 2009 00:18:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=qOAslG+tzEPj2x6+rkor5p12EjFBInPAlDmoDKMskCU=; b=T1ekxRFJmXEMe6eRiCde60HA57rlLF/PLnFAWU+QXXUGIamF/K97uuoH3v7JkJ3woR oZosdpXn3FwB5nOwerfjPK+oCc1IdbuBfRDfHMPI702JkxEIBbx5DgfM0lv+rjLDB0cP Xw/K2PksgjWv/zjzfeSWENcQJzIusV9jL16ME=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=q5uqia0dSaLxKieaEAf26pnAlx8LP4GjdPWUJqhVg7ITua++0MUkDnydtvPoyloDNC vW6LLyUJp6g9X9kMzi48/5qxmQI0/eB83/6fuwCDF00xN7m3WQSjIct4E6AJcyZlwaPk //YZIdsC1q4x/O0i7tSyGmnKSh4eM9udiYh9o=
Received: by 10.223.115.195 with SMTP id j3mr454933faq.99.1234340295618; Wed, 11 Feb 2009 00:18:15 -0800 (PST)
Received: from a88-112-206-87.elisa-laajakaista.fi (a88-112-206-87.elisa-laajakaista.fi [88.112.206.87]) by mx.google.com with ESMTPS id d13sm7928452fka.0.2009.02.11.00.18.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Feb 2009 00:18:15 -0800 (PST)
Message-Id: <A07E9889-3555-40D1-9E12-D71B01665DE9@gmail.com>
From: jouni korhonen <jouni.nospam@gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <2421D12A-7BBE-4148-8D3D-8843E6E8305F@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Last Call: draft-jones-dime-3gpp-eps-command-codes (Diameter Command Code Registration for Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)) to Informational RFC
Date: Wed, 11 Feb 2009 10:18:13 +0200
References: <20090205141701.0E5883A69E6@core3.amsl.com> <2421D12A-7BBE-4148-8D3D-8843E6E8305F@cisco.com>
X-Mailer: Apple Mail (2.930.3)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2009 08:18:14 -0000

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@ietf.org mailing lists by 2009-03-05. Exceptionally,
>> comments may be sent to iesg@ietf.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@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email