Re: [nemo] Potential conflict on NEMOv4 Type and FA-ERR Type

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Fri, 19 May 2006 18:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh9b0-0000nG-Gz; Fri, 19 May 2006 14:21:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh9az-0000mz-Hu for nemo@ietf.org; Fri, 19 May 2006 14:21:05 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh9ax-0001lq-OP for nemo@ietf.org; Fri, 19 May 2006 14:21:05 -0400
Received: from [10.1.201.8] ([10.1.201.8]) by bart.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 May 2006 11:20:58 -0700
Message-ID: <446E0C8A.2010302@azairenet.com>
Date: Fri, 19 May 2006 11:20:58 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [nemo] Potential conflict on NEMOv4 Type and FA-ERR Type
References: <446DF767.7020706@motorola.com>
In-Reply-To: <446DF767.7020706@motorola.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 May 2006 18:20:58.0687 (UTC) FILETIME=[F9F674F0:01C67B70]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: ml-nemo WG <nemo@ietf.org>
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

Alexandru Petrescu wrote:
> 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?

IMO, you should leave it to be assigned by the IANA.
not suggest any value at all. IANA will just pick
the next available one.

Vijay