IETF Logo Mail Archive

Re: [sipcore] consensus call: draft-roach-sipcore-priority-00: IANA registration template needed?

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 29 November 2012 19:15 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D1621F8B9D for <sipcore@ietfa.amsl.com>; Thu, 29 Nov 2012 11:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.154
X-Spam-Level:
X-Spam-Status: No, score=-6.154 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lf1MUYjFAtT0 for <sipcore@ietfa.amsl.com>; Thu, 29 Nov 2012 11:15:15 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 529B721F8B9A for <sipcore@ietf.org>; Thu, 29 Nov 2012 11:15:15 -0800 (PST)
X-AuditID: c1b4fb30-b7f936d0000018b3-e4-50b7b44218fe
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 5F.18.06323.244B7B05; Thu, 29 Nov 2012 20:15:14 +0100 (CET)
Received: from ESESSHC024.ericsson.se (153.88.183.90) by esessmw0191.eemea.ericsson.se (153.88.115.84) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 29 Nov 2012 20:15:13 +0100
Received: from ESESSMB209.ericsson.se ([169.254.9.119]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0318.001; Thu, 29 Nov 2012 20:15:13 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [sipcore] consensus call: draft-roach-sipcore-priority-00: IANA registration template needed?
Thread-Index: AQHNzbbBe6sci1iEWUqAvhw1W5u4NZgAadkwgACKqICAADuEjA==
Date: Thu, 29 Nov 2012 19:15:12 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B049A70@ESESSMB209.ericsson.se>
References: <50A160D8.8030602@alum.mit.edu> <50B68A43.8040605@alum.mit.edu> <50B68E74.3060307@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B048D89@ESESSMB209.ericsson.se>, <50B7902B.2040103@alum.mit.edu>
In-Reply-To: <50B7902B.2040103@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyM+Jvja7Tlu0BBp2fxSxWbDjAavH1xyY2 ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStj9oYJTAXPWCt+H/rM0sC4h6WLkZNDQsBE 4vzSl0wQtpjEhXvr2UBsIYGTjBKfXrFA2DsZJTbvCeli5AKylzBKNP+cCVTEwcEmYCHR/U8b xBQR0JCYtFUNpJxZQFPi0c69YCOFBXIklrf2gY0UEciV6H/xmAXCdpK4vrifHcRmEVCVWH/8 HzvIGF4Bb4k3V+IgNp1nlJhzeDtYPaeAjkT79dtgNiPQmd9PrWGC2CUucevJfKjzBSSW7DnP DGGLSrx8/I8VwlaU+PhqHyNEvY7Egt2f2CBsbYllC1+D1fMKCEqcnPkE6l1tiZbFE9gnMErM QrJiFpL2WUjaZyFpX8DIsoqRPTcxMye93HwTIzCeDm75bbCDcdN9sUOM0hwsSuK8eqr7/YUE 0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwTi334M1XWfZgb2gb+yEe3mfic56rBTZ/7tiQGsu9 a7eZy9qtDzvNDirU++5pfjbz4Ptbc/UXJS9R+1nncciCe9GXT3UyT7Z7P8q+1rTh2QIZTnsu 94sPU35+3M1gtm1T69lC9we1Sm9M9q058rxX+flvYYOEUhUm64Ip9St6pE8fCYp76fpnrhJL cUaioRZzUXEiAC78Glx1AgAA
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] consensus call: draft-roach-sipcore-priority-00: IANA registration template needed?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 19:15:22 -0000

Hi,

>> The important thing is that it is clear to a person who want to register a value WHAT information to provide, and WHERE to send it.
>
> What's necessary is to supply the info that is in the IANA registry. As
> currently proposed, that is only the name of the value and a reference
> to the RFC that defines it.
>
> There is no need to send it anywhere, because it calls for IETF Review,
> which requires an RFC, and the IETF RFC process deals with IANA
> considerations.
>
> It is really hard to write an RFC that defines a new Priority value
> without specifying the name of that value. I think people will remember
> to do this even without a template. :-)

I'll take your word for it :)

Regards,

Christer

v2.23.0 | Report a Bug | By Email