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

Cullen Jennings <fluffy@cisco.com> Wed, 11 February 2009 03:27 UTC

Return-Path: <fluffy@cisco.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 E0E703A69E2 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 19:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level:
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 x1Gnl1S9SfJZ for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 19:27:33 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 25CFD3A67AA for <ietf@ietf.org>; Tue, 10 Feb 2009 19:27:33 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,189,1233532800"; d="scan'208";a="130751422"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 11 Feb 2009 03:27:37 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1B3Rbt0028038 for <ietf@ietf.org>; Tue, 10 Feb 2009 19:27:37 -0800
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1B3RXEp002100 for <ietf@ietf.org>; Wed, 11 Feb 2009 03:27:33 GMT
Message-Id: <2421D12A-7BBE-4148-8D3D-8843E6E8305F@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: ietf@ietf.org
In-Reply-To: <20090205141701.0E5883A69E6@core3.amsl.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
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: Tue, 10 Feb 2009 20:27:33 -0700
References: <20090205141701.0E5883A69E6@core3.amsl.com>
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1492; t=1234322857; x=1235186857; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20Last=20Call=3A=20draft-jones-dime-3gpp- eps-command-codes=20(Diameter=20=20Command=20Code=20Registra tion=20for=20Third=20Generation=20Partnership=20=20Project=2 0(3GPP)=20Evolved=20Packet=20System=20(EPS))=20to=20Informat ional=20RFC |Sender:=20; bh=PQXtm3VBIAYtKUAHYpBUQATG/G1twKV1wvL4EpoBa7E=; b=PCU/VNvuOKW/60qeuuW/hcPVTEceZh2rbTI6HLapPwpmSlvT64hyweMoZT PHtfcgVLbBZW2fenzn6Raacf97ORFqfwrnDpu5kf31/fVywimR8jMJWL7oGs ySqJZtQOkZ;
Authentication-Results: sj-dkim-2; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
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 03:27:34 -0000

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

v2.23.0 | Report a Bug | By Email