draft-soliman-mipshop-4140bis-00 HMIPv6 Update

1
draft-soliman-mipshop-4140bis-00HMIPv6 Update
2
Objectives

• Address the issues raised against RFC 4140
• Move the new version to PS.

3
Issues raised against RFC 4140

• Issues were raised in public or private based on
  implementations or design decisions.
• Issue 1 Expand Security to include allow for
  cases where the MN is not configured with a
  certificate
• Issue 2 Scalability of Dynamic MAP Discovery
• Issue 3 Integration of the AR in the signalling
  path to allow for triggering AR functions like
  CT.
• Issue 4 Tightening up the spec language, e.g.
  making sure that HMIPv6 can be used without
  mandating that the MN has a permanent HA.
• Issue 5 Support for new functions that were
  added to MIPv6 since the spec was published
  Mobile networks, DSMIP, flow movement .etc.

4
Issue 1 Expand Security to include allow for
cases where the MN is not configured with a
certificate

• This issue was discussed in Paris
• Agreement to add IKEv2 support with EAP and
  clarify its use in the new spec
• Other security alternatives are being
  standardised separately.

5
Issue 5 Support for new functions that were
added to MIPv6 since the spec was published
Mobile networks, DSMIP, flow movement .etc.

• The new spec needs to list all possible options
  that can be added to the Local BU.
• Where appropriate, describe applicability or any
  new behaviour
• Most options do not require any new behaviour,
  but its useful to mention that in the spec.

6
Issue 3 Integration of the AR in the signalling
path to allow for triggering AR functions like
CT.

• HMIPv6 removes the AR from the signalling path
  because the routing switch is done in the MAP
  (core network)
• This is useful for routing purposes but in many
  cases the AR needs to be made aware that a
  handover is taking place to send the MNs context
  to a new AR
• Suggestion Add hooks to inform the AR of the
  handover while maintaining the BU reception in
  the MAP.