Re: [Autoconf] Closing summary on consensus-call for RFC5889modifications

["Dearlove, Christopher (UK)" <[e-mail]>]

Can you outline such a case. It's not the simple use of Mobile IP
noted below as for that router prefix autoconfiguration is sufficient.

-- 
Christopher Dearlove
Technology Leader, Communications Group
Communications and Networks Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: [phone]  Fax: [phone]

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87,
Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: Charles E. Perkins [mailto:[e-mail]] 
Sent: 27 August 2010 19:42
To: Dearlove, Christopher (UK)
Cc: [e-mail]
Subject: Re: [Autoconf] Closing summary on consensus-call for
RFC5889modifications


                    *** WARNING ***

  This message has originated outside your organisation,
  either from an external partner or the Global Internet. 
      Keep this in mind if you answer this message.
 

Hello Chris,

On 8/27/2010 5:27 AM, Dearlove, Christopher (UK) wrote:
> There's a key question as to how much functionality.

This is an important point.  The functionality needed by
a host in order to connect to network depends on the
functionality provided by the router that offers the
netwok prefix.

> If a node just has a single point of attachment to an unchanging
> router, then router prefix autoconf is sufficient, as the host
> node can just get an address from its router. If we extend that
> so that it can now move, and use Mobile IP with its home location
> being the router it first attached to, ditto.

Check.

> The question is what is the case where the host node is doing
> something useful, but can't just get an address delegated to
> it by an autoconfed router?
>
> (I am not saying I don't think there is such a case. I'm just
> saying I haven't seen it - quite a different thing.)

Well, there are such cases, and they should be allowed.

Regards,
Charlie P.




********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************