IETF Logo Mail Archive

Re: [nemo] new requirement for draft-ietf-nemo-requirements

Jari Arkko <jari.arkko@piuha.net> Tue, 12 December 2006 10:29 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gu4t8-0007Ab-2T; Tue, 12 Dec 2006 05:29:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gu4t6-0007AV-Ok for nemo@ietf.org; Tue, 12 Dec 2006 05:29:28 -0500
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gu4t3-00047W-FR for nemo@ietf.org; Tue, 12 Dec 2006 05:29:28 -0500
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8C11B89837; Tue, 12 Dec 2006 12:29:20 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 4751289834; Tue, 12 Dec 2006 12:29:20 +0200 (EET)
Message-ID: <457E8480.3030308@piuha.net>
Date: Tue, 12 Dec 2006 12:29:20 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.8 (X11/20061117)
MIME-Version: 1.0
To: IETF NEMO WG <nemo@ietf.org>, Ross Callon <rcallon@juniper.net>
Subject: Re: [nemo] new requirement for draft-ietf-nemo-requirements
References: <45743493.3010403@piuha.net>
In-Reply-To: <45743493.3010403@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc:
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Errors-To: nemo-bounces@ietf.org

Thanks for your responses. I added a note to the
RFC Editor to insert the requirement. Ross, I believe
you can clear your Discuss now. Thanks.

I will also look at the new charter with the
chairs and consider if it needs to say something
about this, or if the reference to this RFC will
be enough.

--Jari

v2.23.0 | Report a Bug | By Email