[nemo] Potential conflict on NEMOv4 Type and FA-ERR Type
Alexandru Petrescu <alexandru.petrescu@motorola.com> Fri, 19 May 2006 16:50 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh8Bj-0000pO-3d; Fri, 19 May 2006 12:50:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh8Bi-0000pI-5m for nemo@ietf.org; Fri, 19 May 2006 12:50:54 -0400
Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh8Bg-00045P-OK for nemo@ietf.org; Fri, 19 May 2006 12:50:54 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id k4JGon0d011130 for <nemo@ietf.org>; Fri, 19 May 2006 09:50:49 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k4JGomHe003686 for <nemo@ietf.org>; Fri, 19 May 2006 11:50:49 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 28B65865980 for <nemo@ietf.org>; Fri, 19 May 2006 18:50:48 +0200 (CEST)
Message-ID: <446DF767.7020706@motorola.com>
Date: Fri, 19 May 2006 18:50:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: ml-nemo WG <nemo@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [nemo] Potential conflict on NEMOv4 Type and FA-ERR Type
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
I've been pointed that there seems to be a potential conflict on NEMOv4 Mobile Network Extension Type and FA-Err Type. NEMOv4 uses a new Type (to be assigned by IANA) in Mobile Network Extension. We suggested in the draft that it be 45. FA-ERR draft-ietf-mip4-faerr-02.txt uses Type 45 for FA Error Extension (already assigned by IANA). The draft does not specify 45, just says TBA by IANA. IANA seems to have assigned it, see http://www.iana.org/assignments/mobileip-numbers. draft-ietf-mobileip-gen-key-01.txt implemented in dynamics 0.8.1 uses 45 too, but I think this can be ignored, because I think this work has been evolved into draft-rfc3012bis which uses Type 24. To solve the issue between NEMOv4 and FA-ERR I suggest that we use Type 46 - and not 45 - in NEMOv4 implementation, until IANA assigns a Type for NEMOv4 Mobile Network Extension. What do you think? Alex
- [nemo] Potential conflict on NEMOv4 Type and FA-E… Alexandru Petrescu
- RE: [nemo] Potential conflict on NEMOv4 Type and … Narayanan, Vidya
- Re: [nemo] Potential conflict on NEMOv4 Type and … Vijay Devarapalli
- RE: [nemo] Potential conflict on NEMOv4 Type and … Tsirtsis, George
- Re: [nemo] Potential conflict on NEMOv4 Type and … Henrik Levkowetz
- Re: [nemo] Potential conflict on NEMOv4 Type and … Henrik Levkowetz
- RE: [nemo] Potential conflict on NEMOv4 Type and … Narayanan, Vidya