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

"Narayanan, Vidya" <vidyan@qualcomm.com> Fri, 19 May 2006 18:05 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh9MK-0005o9-Rq; Fri, 19 May 2006 14:05:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh9MJ-0005o4-Ny for nemo@ietf.org; Fri, 19 May 2006 14:05:55 -0400
Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh9MI-00013F-Ac for nemo@ietf.org; Fri, 19 May 2006 14:05:55 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k4JI5ocb014367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 May 2006 11:05:53 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com [129.46.134.172]) by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k4JI5meX003278; Fri, 19 May 2006 11:05:50 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 May 2006 11:05:26 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [nemo] Potential conflict on NEMOv4 Type and FA-ERR Type
Date: Fri, 19 May 2006 11:05:25 -0700
Message-ID: <2EBB8025B6D1BA41B567DB32C1D8DB84882B16@NAEX06.na.qualcomm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [nemo] Potential conflict on NEMOv4 Type and FA-ERR Type
Thread-Index: AcZ7ZK/HAAS9bVODSmafdrd333h8mAAChnqQ
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>, ml-nemo WG <nemo@ietf.org>
X-OriginalArrivalTime: 19 May 2006 18:05:26.0057 (UTC) FILETIME=[CE126990:01C67B6E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

Sounds good to me.  

> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com] 
> Sent: Friday, May 19, 2006 9:51 AM
> To: ml-nemo WG
> Subject: [nemo] Potential conflict on NEMOv4 Type and FA-ERR Type
> 
> 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
> 
>