[Enum] Reference to E.164
"Nieminen Klaus" <Klaus.Nieminen@ficora.fi> Mon, 06 November 2006 11:14 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gh2RL-0004Ra-SG; Mon, 06 Nov 2006 06:14:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gh2RK-0004RQ-NQ for enum@ietf.org; Mon, 06 Nov 2006 06:14:54 -0500
Received: from mail.ficora.fi ([194.100.96.25] helo=portti1.ficora.fi) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gh2RG-0001uI-SM for enum@ietf.org; Mon, 06 Nov 2006 06:14:54 -0500
Received: from POSTI.laru.local ([10.1.0.10]) by portti1.ficora.fi with InterScan Messaging Security Suite; Mon, 06 Nov 2006 13:14:42 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 06 Nov 2006 13:14:42 +0200
Message-ID: <07BC6C0D40216E44A34BE6701694FE8603BE2869@POSTI.laru.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Reference to E.164
Thread-Index: AcamjzwfCz1CDf2+TOCZ0/3GlcplrwC+7iewFgHoxr0=
References: <07BC6C0D40216E44A34BE6701694FE86038B46DD@POSTI.laru.local>
From: Nieminen Klaus <Klaus.Nieminen@ficora.fi>
To: enum@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Subject: [Enum] Reference to E.164
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2044813385=="
Errors-To: enum-bounces@ietf.org
Hi all, Just want to repeat my earlier comment, because nearly every reference in the IDs in our agenda point to a old version of E.164 Recommendation. Please use 02/05: http://www.itu.int/rec/T-REC-E.164/en List of IDs that should be corrected in the next version: - draft-ietf-enum-3761bis-00.txt - draft-ietf-enum-uri-00.txt - draft-chenh-enum-app-auth-00.txt - draft-reichinger-enum-foaf-01.txt - draft-ietf-enum-iax-01.txt - draft-ietf-enum-combined-01.txt - Klaus ________________________________ Lähettäjä: Nieminen Klaus [mailto:Klaus.Nieminen@ficora.fi] Lähetetty: ma 17.7.2006 13:30 Vastaanottaja: enum@ietf.org Aihe: RE: [Enum] ENUM Working Group last call fordocumentdraft-ietf-enum-validation-token-01.txt Hi all, I have one minor issue that I believe to be valid for most current ENUM IDs. The old E.164 Recommendation has been replaced by a new one E.164 (02/05. For more details see: http://www.itu.int/rec/T-REC-E.164/en It's not critical, but I think we should start using the latest version. regards, - Klaus -
_______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
- RE: [Enum] ENUM Working Group last call for docum… Nieminen Klaus
- [Enum] Reference to E.164 Nieminen Klaus