Re: [netext] RE : Re: I-D Action: draft-ietf-netext-pd-pmip-03.txt

BOC Michael <michael.boc@cea.fr> Fri, 20 July 2012 07:19 UTC

Return-Path: <michael.boc@cea.fr>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB36E21F853C; Fri, 20 Jul 2012 00:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.123
X-Spam-Level:
X-Spam-Status: No, score=-8.123 tagged_above=-999 required=5 tests=[AWL=2.125, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vnny32d2a5Sb; Fri, 20 Jul 2012 00:19:04 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id DAB8C21F8526; Fri, 20 Jul 2012 00:19:03 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id q6K7JvuV009468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 20 Jul 2012 09:19:57 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id q6K7JvfG024908; Fri, 20 Jul 2012 09:19:57 +0200 (envelope-from michael.boc@cea.fr)
Received: from EXCAH-A2.intra.cea.fr (excah-a2.intra.cea.fr [132.166.88.76]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id q6K7JuqC031826; Fri, 20 Jul 2012 09:19:56 +0200
Received: from EXDAG0-B3.intra.cea.fr ([fe80::d0da:1b48:7560:ee73]) by EXCAH-A2.intra.cea.fr ([fe80::1424:a20d:95ab:8077%11]) with mapi id 14.01.0339.001; Fri, 20 Jul 2012 09:19:56 +0200
From: BOC Michael <michael.boc@cea.fr>
To: "zhou.xingyue@zte.com.cn" <zhou.xingyue@zte.com.cn>
Thread-Topic: RE : Re: [netext] I-D Action: draft-ietf-netext-pd-pmip-03.txt
Thread-Index: AQHNYvKCvhAGL3znHEuOVmE7wTRHpJcrmk7ggAW68ICAAGMMZf//4QuAgAAp9bA=
Date: Fri, 20 Jul 2012 07:19:55 +0000
Message-ID: <94D2EEADE1F74740979E8041CBA339380355ACBF@EXDAG0-B3.intra.cea.fr>
References: <94D2EEADE1F74740979E8041CBA339380355AC67@EXDAG0-B3.intra.cea.fr> <OF97EFFCA1.0B541570-ON48257A41.0022FF38-48257A41.00233DC9@zte.com.cn>
In-Reply-To: <OF97EFFCA1.0B541570-ON48257A41.0022FF38-48257A41.00233DC9@zte.com.cn>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [132.166.88.106]
x-tm-as-product-ver: SMEX-10.0.0.4211-6.800.1017-19052.002
x-tm-as-result: No--40.293200-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_94D2EEADE1F74740979E8041CBA339380355ACBFEXDAG0B3intrace_"
MIME-Version: 1.0
Cc: "netext@ietf.org" <netext@ietf.org>, "netext-bounces@ietf.org" <netext-bounces@ietf.org>
Subject: Re: [netext] RE : Re: I-D Action: draft-ietf-netext-pd-pmip-03.txt
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 07:19:05 -0000

Joy,

Ok so I guess for you the initial attachment procedure is the PBU sent for HNPs. Right?
If so:
Do you mean you don’t set the flag in subsequent PBUs ?
Do you mean the LMA has to do something special when it receives the R flag that it will not do when receiving the MNP option set to zero?
Do you mean the check of policy profile for the MR is “stateless” (the MAG do not store the fact that the MR needs MNPs)?

Michael

De : zhou.xingyue@zte.com.cn [mailto:zhou.xingyue@zte.com.cn]
Envoyé : vendredi 20 juillet 2012 08:25
À : BOC Michael
Cc : netext@ietf.org; netext-bounces@ietf.org
Objet : 答复: RE : Re: [netext] I-D Action: draft-ietf-netext-pd-pmip-03.txt


Hello,

You can double check the draft which says the R flag is set during the initial attachment procedure.

Joy

BOC Michael <michael.boc@cea.fr<mailto:michael.boc@cea.fr>>

2012-07-20 14:17

收件人

"zhou.xingyue@zte.com.cn<mailto:zhou.xingyue@zte.com.cn>" <zhou.xingyue@zte.com.cn<mailto:zhou.xingyue@zte.com.cn>>

抄送

"netext@ietf.org<mailto:netext@ietf.org>" <netext@ietf.org<mailto:netext@ietf.org>>, "netext-bounces@ietf.org<mailto:netext-bounces@ietf.org>" <netext-bounces@ietf.org<mailto:netext-bounces@ietf.org>>

主题

RE : Re: [netext] I-D Action: draft-ietf-netext-pd-pmip-03.txt







Hi,


By the way, if the MAG sends a MNPs option set to 0 in the PBU it is redundant to set a flag to understand it is for a mobile router.


Michael
________________________________

De : zhou.xingyue@zte.com.cn<mailto:zhou.xingyue@zte.com.cn> [zhou.xingyue@zte.com.cn]
Date d'envoi : vendredi 20 juillet 2012 04:21
À : BOC Michael
Cc : i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>; internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>; netext@ietf.org<mailto:netext@ietf.org>; netext-bounces@ietf.org<mailto:netext-bounces@ietf.org>
Objet : 答复: Re: [netext] I-D Action: draft-ietf-netext-pd-pmip-03.txt


Hi,

The purpose of setting R flag is to indicate the network that network mobility service is allowed to the mobile node as specified in section 3.2. In this draft, it just focus on the way to assign the MNP to the MR based on DHCPv6-PD triggering mechanism.

Regarding the possible hints in IA_PD(s), I dont get your point very much. Could you explain more?

Best Regards,
Joy

netext-bounces@ietf.org<mailto:netext-bounces@ietf.org> 写于 2012-07-16 17:12:56:

> Hello all,
>
> Concerning this draft, I would like to know why you need to set the
> R flag in PBU
> (because you don't explain it in the draft) and if your approach is
> to not take
> into account possible hints in IA_PD(s). If this is the case, we
> just have to provide
> MNP(s) at MR attachment with the HNP(s) and we move on another subject.
>
> Regards,
>
>
> Michael
>
>
> > -----Message d'origine-----
> > De : netext-bounces@ietf.org<mailto:netext-bounces@ietf.org> [mailto:netext-bounces@ietf.org] De la
> > part de internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
> > Envoyé : lundi 16 juillet 2012 03:29
> > À : i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
> > Cc : netext@ietf.org<mailto:netext@ietf.org>
> > Objet : [netext] I-D Action: draft-ietf-netext-pd-pmip-03.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >  This draft is a work item of the Network-Based Mobility Extensions
> > Working Group of the IETF.
> >
> >    Title           : Prefix Delegation for Proxy Mobile IPv6
> >    Author(s)       : Xingyue Zhou
> >                           Jouni Korhonen
> >                           Carl Williams
> >                           Sri Gundavelli
> >                           Carlos J. Bernardos
> >    Filename        : draft-ietf-netext-pd-pmip-03.txt
> >    Pages           : 16
> >    Date            : 2012-07-15
> >
> > Abstract:
> >    Proxy Mobile IPv6 enables IP mobility for a host without requiring
> >    its participation in any mobility signaling, being the network
> >    responsible for managing IP mobility on behalf of the host.
> > However,
> >    Proxy Mobile IPv6 does not support assigning a prefix to a router
> > and
> >    managing its IP mobility.  This document specifies an extension to
> >    Proxy Mobile IPv6 protocol for supporting network mobility using
> >    DHCPv6-based Prefix Delegation.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-netext-pd-pmip
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-netext-pd-pmip-03
> >
> > A diff from previous version is available at:
> > http://tools.ietf.org/rfcdiff?url2=draft-ietf-netext-pd-pmip-03
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > netext mailing list
> > netext@ietf.org<mailto:netext@ietf.org>
> > https://www.ietf.org/mailman/listinfo/netext
> _______________________________________________
> netext mailing list
> netext@ietf.org<mailto:netext@ietf.org>
> https://www.ietf.org/mailman/listinfo/netext
>