DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
 h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
 b=r11XV9VNdWPpw/I6GgU2csdi01mBkUhvrxREgy3VVkWX08o1+Hm4yV0Cztaea2zPFGlq54WYoPwd9WNyN+LlwySHpkFC9uEZ0QN6TlhHPHocsKaeoVgPnyDsGEwkAgOszn7pjy1zY8zquf7MEGrgbKyfChDlZ5c1jRufA5y8uXA=;
Message-ID: <165516.11213.qm@web111411.mail.gq1.yahoo.com>
References: <C8B03E68.14FA4%hesham@elevatemobile.com>
 <4C8A1DEF.9050403@gmail.com>
 <BF345F63074F8040B58C00A186FCA57F1F6826E30A@NALASEXMB04.na.qualcomm.com>
Date: Mon, 13 Sep 2010 08:55:59 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix
 Delegation for NEMO) to Proposed Standard
To: "Laganier, Julien" <julienl@qualcomm.com>,
 Alexandru Petrescu <alexandru.petrescu@gmail.com>,
 Hesham Soliman <hesham@elevatemobile.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1F6826E30A@NALASEXMB04.na.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>, mext <mext@ietf.org>
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>

=0A=0A----- Original Message ----=0A> From: "Laganier, Julien" <julienl@qua=
lcomm.com>=0A> To: Alexandru Petrescu <alexandru.petrescu@gmail.com>; Hesha=
m Soliman =0A><hesham@elevatemobile.com>=0A> Cc: IETF Discussion <ietf@ietf=
.org>; mext <mext@ietf.org>=0A> Sent: Fri, September 10, 2010 11:57:36 AM=
=0A> Subject: Re: [MEXT] Last Call: draft-ietf-mext-nemo-pd (DHCPv6 Prefix =
=0A>Delegation for NEMO) to Proposed Standard=0A> =0A> Alexandru Petrescu w=
rote:=0A> > =0A> > Le 10/09/2010 11:58, Hesham Soliman a  =E9crit :=0A> > >=
=0A> > > On 10/09/10 7:55 PM, "Alexandru=0A> > >  Petrescu"<alexandru.petre=
scu@gmail.com>  wrote:=0A> > >=0A> > >> Le 10/09/2010 11:48, Hesham Soliman=
 a =E9crit  :=0A> > >>>>>=0A> > >>>>> =3D>     Who cares, specify it in you=
r product description. The=0A> >  >>>>>       IETF doesn't specify how to b=
uild  products.=0A> > >>>>=0A> > >>>> Hmm... to me it is a  very IETF sensi=
tive issue the Router vs=0A> > >>>> Host. For  example, an ND spec says dis=
tinctively what a Host=0A> > >>>> and  what a Router does, e.g. a Host does=
 not respond to Router=0A> >  >>>>  Solicitation.=0A> > >>>=0A> > >>>  =3D>=
   Yes and it does so on a per-interface basis, not on a=0A> >  >>> per-mac=
hine basis.=0A> > >>=0A> > >> Yes, and the  Mobile Router is a Router on it=
s egress interface=0A> > >> when  connected at home, as per spec.  It is th=
at interface that=0A> > >>  needs a default route automatically configured.=
=0A> > >=0A> > >  =3D>  Ok, so you're happy with it being half host half ro=
uter when  it's=0A> > > away from home?=0A> > =0A> > When it is away from h=
ome it  is fully a Host on the egress interface.=0A> > When at home fully R=
outer on  same.  I am happy with it this way.=0A> > =0A> > > If so then let=
 it  do the same at home. Otherwise, I don't know how=0A> > > you want to f=
ix  this in this WG.=0A> > =0A> > It would mean to specify it to be a at ho=
me,  be first a Host (get=0A> > default route) then change and become a Rou=
ter, but  still at home.=0A> >=0A> > This behaviour could be set in the DHC=
Pv6-PD-NEMO  draft, being under=0A> > discussion now.=0A> =0A> This is a no=
n issue for this  draft. This is not specific to NEMO but generic =0A>to an=
y DHCPv6 Prefix Delegation  setup where the requesting router needs to =0A>=
configures an address on its north  side. It can do so as per the deploymen=
t =0A>specifics, including, but not limited  to, acting as a host on the no=
rth =0A>interface and as a router on south interfaces  -- please remember t=
hat Neighbor =0A>Discovery is specified on a per-interface  basis.=0A> =0A>=
 [ I also note that this draft has been more than 2 years in the  MEXT work=
ing =0A>group in which you are participating, which gave you ample time to =
 comment on =0A>this and other things...  ]=0A> =0A=0AJulien: Alex, myself,=
 possibly others have been raising issues with this draft =0Asince long tim=
e.=0A=0AIt is not new.=0A=0ARegards,=0A=0Abehcet=0A=0A=0A=0A