RE: [nemo] NEMOv4 vs DS-MIPv6

"Soliman, Hesham" <hsoliman@qualcomm.com> Thu, 11 May 2006 18:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeFVG-0002cZ-2J; Thu, 11 May 2006 14:03:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeFVE-0002cP-At for nemo@ietf.org; Thu, 11 May 2006 14:03:08 -0400
Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeFVC-0005NK-Vx for nemo@ietf.org; Thu, 11 May 2006 14:03:08 -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 k4BI35Rq008413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 11 May 2006 11:03:05 -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 k4BI30nx009524; Thu, 11 May 2006 11:03:04 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 May 2006 11:03:01 -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] NEMOv4 vs DS-MIPv6
Date: Thu, 11 May 2006 11:02:59 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF00284A12D@NAEX06.na.qualcomm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [nemo] NEMOv4 vs DS-MIPv6
Thread-Index: AcZ1I7qPjvI9CUuGSwij04KymJ7F5wAAVCvQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 11 May 2006 18:03:01.0107 (UTC) FILETIME=[245ECC30:01C67525]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: nemo@ietf.org, thierry.ernst@inria.fr, henrik@levkowetz.com
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

It is in the published draft. We don't talk about MNP tables but 
that doesn't mean we don't support it. 

Hesham
 

 > -----Original Message-----
 > From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com] 
 > Sent: Thursday, May 11, 2006 1:52 PM
 > To: Soliman, Hesham
 > Cc: Keiichi SHIMA; nemo@ietf.org; thierry.ernst@inria.fr; 
 > henrik@levkowetz.com
 > Subject: Re: [nemo] NEMOv4 vs DS-MIPv6
 > 
 > Soliman, Hesham wrote:
 > > 
 > >>> Tsirtsis, George wrote:
 > >>>> P.S.: BTW, Hesham is telling me that DS-MIPv6 spec does
 > >> support IPv4
 > >>>> prefixes
 > >>> 
 > >>> ... where?  The draft only says MR should attach a
 > >> prefixlen on the v4
 > >>> HoA in a IPv4 hoa option.  Is there a way to communicate
 > >> v4 MNPs that
 > >>> are not related to the HoA?  Is it possible to specify
 > >> several v4 MNPs?
 > >> 
 > >> I think I raised the feature in the Vancouver meeting and 
 > I believe
 > >>  authors incorporated the function to carry multiple 
 > v4pfxes in the
 > >>  draft.
 > >> 
 > >> The issue 57 is that proposal I raised, and it seems it had been 
 > >> accepted.
 > >> 
 > >> Maybe a short status report of this topic from the authors make 
 > >> your question clear.
 > > 
 > > => What Keiichi said is correct. We included this based on his 
 > > comments.
 > 
 > Ah I see, thanks.  I based my remarks on the published draft.  I'll
 > wait for the next draft cycle to see whether MNP can be 
 > different than
 > HoA, and I will comment then.
 > 
 > Alex
 >